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
- Subject: Re: MEM_COPY_ATTRIBUTES
- From: Mark Mitchell <mark at codesourcery dot com>
- Date: Wed, 03 May 2000 11:20:08 -0700
- Cc: gcc at gcc dot gnu dot org
- Organization: CodeSourcery, LLC
- References: <10005031806.AA27783@vlsi1.ultra.nyu.edu>
>>>>> "Richard" == Richard Kenner <kenner@vlsi1.ultra.nyu.edu> writes:
Richard> I also *just* noticed that it also doesn't copy
Richard> RTX_UNCHANGING_P. Shouldn't it? *That* was the initial
Richard> bug I found in alter_subreg, but I now see that it wasn't
Richard> fixed by the use of this macro.
I don't know. I don't see why if one MEM is unchanging another one
should be, just because it happens to have the same volatility, and
scalarness, say.
It might again be reasonable for MEM_COPY_ATTRIBUTES to take an
UNCHANGING_P parameter so that users were forced to decide this issue
-- but I don't think just copying is right.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com