This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Proposed resolution to aliasing issue.
- From: Daniel Berlin <dberlin at dberlin dot org>
- To: Dale Johannesen <dalej at apple dot com>
- Cc: Mark Mitchell <mark at codesourcery dot com>, gcc mailing list <gcc at gcc dot gnu dot org>
- Date: Wed, 11 May 2005 18:29:37 -0400 (EDT)
- Subject: Re: Proposed resolution to aliasing issue.
- References: <428251FD.7030702@codesourcery.com> <176d568e0d5e48cac0ea8f4513cde02a@apple.com>
The attribute might well be unnecessary, and once it's in it's in forever.
And I suspect supporting
different semantics for different calls will create problems down the line,
somehow or other
(although I confess I don't think of any offhand).
Attributes and flags have more or less the same effect from the POV of
something like a call graph partitioner, (other stuff we'll hopefully have
down the line).
It's just that now you have "incompatible" compilation units, instead of
"incompatible" functions.
So there really isn't a good reason to have one and not the other, unless
we believe we are going to screw up the smenatics :)