This is the mail archive of the gcc@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: TREE_UNCHANGING?

From: Jason Merrill <jason at redhat dot com>
To: Richard Henderson <rth at redhat dot com>
Cc: gcc at gcc dot gnu dot org
Date: Wed, 08 May 2002 23:03:44 +0100
Subject: Re: TREE_UNCHANGING?
References: <wvld6w6x0go.fsf@prospero.cambridge.redhat.com><20020508132651.C14996@redhat.com>

>>>>> "Richard" == Richard Henderson <rth@redhat.com> writes:

> On Wed, May 08, 2002 at 01:56:07PM +0100, Jason Merrill wrote:
>> It seems that setting TREE_CONSTANT on the INDIRECT_REF does what I want,
>> thanks to the check in set_mem_attributes; would it make sense to bless
>> this usage?

> No.  I want to remove RTX_UNCHANGING_P altogether.

> You should be able to force-assign a unique alias set to a vtable though.

I don't think that would help; a call is considered to change arbitrary
memory.  A unique alias set still conflicts with alias set 0.

Jason

Follow-Ups:
- Re: TREE_UNCHANGING?
  - From: Jason Merrill

References:
- TREE_UNCHANGING?
  - From: Jason Merrill
- Re: TREE_UNCHANGING?
  - From: Richard Henderson

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