This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] PR middle-end/14289: TREE_STATIC global reg vars

From: Zack Weinberg <zack at codesourcery dot com>
To: Richard Henderson <rth at redhat dot com>
Cc: Roger Sayle <roger at eyesopen dot com>, Gabriel Dos Reis <gdr at integrable-solutions dot net>, gcc-patches at gcc dot gnu dot org
Date: Thu, 04 Mar 2004 15:20:18 -0800
Subject: Re: [PATCH] PR middle-end/14289: TREE_STATIC global reg vars
References: <Pine.LNX.4.44.0403032049540.3603-100000@www.eyesopen.com><874qt5jia3.fsf@egil.codesourcery.com><20040304231022.GA9269@redhat.com>

Richard Henderson <rth@redhat.com> writes:

> On Wed, Mar 03, 2004 at 09:25:08PM -0800, Zack Weinberg wrote:
>> why do we have both TREE_STATIC and TREE_PUBLIC?
>
> STATIC means !automatic, i.e. lives in memory outside any
> stack frame.  PUBLIC means it is visible to other translation
> units, i.e. has .global applied to it at the assembly level.
>
> Not sure what makes most sense for a global register variable;
> probably PUBLIC.

Thanks.

zw

References:
- Re: [PATCH] PR middle-end/14289: TREE_STATIC global reg vars
  - From: Roger Sayle
- Re: [PATCH] PR middle-end/14289: TREE_STATIC global reg vars
  - From: Zack Weinberg
- Re: [PATCH] PR middle-end/14289: TREE_STATIC global reg vars
  - From: Richard Henderson

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]