This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: type based aliasing again
- To: craig at jcb-sc dot com
- Subject: Re: type based aliasing again
- From: David Edelsohn <dje at watson dot ibm dot com>
- Date: Tue, 14 Sep 1999 18:05:54 -0400
- Cc: nik at tiuk dot ti dot com, richard dot earnshaw at arm dot com, N8TM at aol dot com, gcc at gcc dot gnu dot org, espie at quatramaran dot ens dot fr
>>>>> craig writes:
craig> (I won't even get into the stunning news that the FSF has reportedly
craig> just changed the rules of the very difficult job of compiler development,
craig> apparently *since* the EGCS team agreed to become GCC and under the
craig> aegis of the FSF.)
How is asking that the compiler try to provide compatibility by
default where it is easy, such as not coupling -fstrict-aliasing to a -O#
level, an unreasonable and burdensome request? This is a one-line change
removing flag_strict_aliasing from optimize >= 2 stanza in toplev.c. You
are arguing against an interpretation of the request that takes it to an
extreme, not the request itself.
David