This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [dax@gurulabs.com: PATCH: `__norestrict' type qualifier (fwd)]
- To: Jamie Lokier <jamie.lokier AT cern.ch>
- Subject: Re: [dax@gurulabs.com: PATCH: `__norestrict' type qualifier (fwd)]
- From: Jeffrey A Law <law AT cygnus dot com>
- Date: Tue, 14 Sep 1999 19:39:51 -0600
- cc: "Patrick J. LoPresti" <patl AT cag.lcs.mit dot edu>, gcc AT egcs.cygnus dot com, rms AT gnu dot org
- Reply-To: law AT cygnus dot com
In message <19990914173757.B12177@pcep-jamie.cern.ch>you write:
> Patrick J. LoPresti wrote:
> > used to resolve any arguments about the behavior of the extension.
>
> To conform to this, you need to fix up the other type-based alias
> analysis that's been in the compiler for a long time: MEM_IN_STRUCT_P.
> That would be a good thing, because currently -fno-strict-aliasing does
> not turn off this alias assumption.
>
> Perhaps MEM_IN_STRUCT_P can be completely removed now there is a general
> type alias framework?
MEM_IN_STRUCT_P is still valuable according to my tests a few months ago.
I'm curious, what code do you (or anyone) have that violates the
MEM_IN_STRUCT_P
assumptions. [As opposed to bugs in MEM_IN_STRUCT_P, of which there have been
many, but with the revamp from last year, it ought to be correct now. ]
jeff