This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: FAIL: gcc.c-torture/execute/950628-1.c execution, -O1
- To: rth at redhat dot com
- Subject: Re: FAIL: gcc.c-torture/execute/950628-1.c execution, -O1
- From: kenner at vlsi1 dot ultra dot nyu dot edu (Richard Kenner)
- Date: Wed, 24 Jan 01 19:22:36 EST
- Cc: gcc-patches at gcc dot gnu dot org
Why bother calling /u temporaries "unchanging" if we're going to
have them change? I think that notion is just downright confusing.
True. Basically it just provides a second level of anti-aliasing.
I think the only sensible alternatives are (1) don't reuse /u slots
at all, or (2) don't create /u slots at all.
I don't think (2) is viable because if you have a pointer to constant
and that's in a temp slot (e.g., a local variable), you'll be doing /u
accesses to temp slots. So I guess that (1) is the only option, though
it does seem quite costly.
I wish there were a better way.