This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Proposal: -O4 -> strict-aliasing
- To: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Subject: Re: Proposal: -O4 -> strict-aliasing
- From: Alexandre Oliva <oliva at lsd dot ic dot unicamp dot br>
- Date: 31 Oct 1999 23:41:33 -0200
- Cc: Andris Pavenis <andris at stargate dot astr dot lu dot lv>, Mark Mitchell <mark at codesourcery dot com>, nbecker at fred dot net, gcc at gcc dot gnu dot org
- References: <Pine.GSO.4.20.9910300319390.9832-100000@alphard.dbai.tuwien.ac.at>
On Oct 29, 1999, Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> wrote:
> On Wed, 27 Oct 1999, Andris Pavenis wrote:
>> Perhaps one who needs -fstrict-aliasing with 2.95.2 could simply modify
>> specs by adding '%(!no-strict-aliasing: -fstrict-aliasing)' to cc1_spec
>> (or one can do the oposite with gcc-2.95.1 and gcc-2.95 to disable strict
>> aliasing). So the default can be simply changed.
>>
>> Maybe such hack should be mentioned in FAQ.
> Personally I don't think we should add that to the FAQ, but if others feel
> differently, please let me know, I don't have any strong preference.
Someone wrote before that we shouldn't teach people to modify their
spec files, as this generally leads to irreproducible bug reports,
because of the hidden arguments passed to the compiler.
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{lsd.ic.unicamp.br,guarana.{org,com}} aoliva@{acm,computer}.org
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
** I may forward mail about projects to mailing lists; please use them