This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: MEM_COPY_ATTRIBUTES
- To: mark at codesourcery dot com
- Subject: Re: MEM_COPY_ATTRIBUTES
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Date: Wed, 3 May 00 14:25:08 EDT
- Cc: gcc at gcc dot gnu dot org
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.
The idea is that it's referencing the same thing, or a part of the
same thing.
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.
So far the first few cases I saw are copying it too. I'll take a look
at each usage and see what's right. My best guess is that it's unlikely
that not copying it is ever right.