This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: MEM_COPY_ATTRIBUTES
- To: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Subject: Re: MEM_COPY_ATTRIBUTES
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Wed, 03 May 2000 11:07:07 -0600
- cc: mark at codesourcery dot com, gcc at gcc dot gnu dot org
- Reply-To: law at cygnus dot com
In message <10005031708.AA27028@vlsi1.ultra.nyu.edu>you write:
> No, because the new MEM starts out in alias set zero, which is the
> special "aliases anything" alias set.
>
> What about the case where we make a MEM with a PUT_CODE? That's the
> case (in alter_reg) that started me thinking in this direction.
This is handled by explicitly initializing MEM_ALIAS_SET to zero.
An optimization that could be performed here is to get an alias
set which applies to stack slots for reload's use and use it for all
MEMs created by alter_reg since we know those slots can't alias with
anything else.
jeff