This is the mail archive of the
mailing list for the GCC project.
Re: changing "configure" to default to "gcc -g -O2 -fwrapv ..."
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Diego Novillo <dnovillo at redhat dot com>
- Cc: Mark Mitchell <mark at codesourcery dot com>, Ian Lance Taylor <iant at google dot com>, Paul Eggert <eggert at CS dot UCLA dot EDU>, autoconf-patches at gnu dot org, bug-gnulib at gnu dot org, gcc at gcc dot gnu dot org
- Date: 03 Jan 2007 00:13:40 +0100
- Subject: Re: changing "configure" to default to "gcc -g -O2 -fwrapv ..."
- References: <email@example.com> <20061220123349.GE7947@iam.uni-bonn.de> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <459AD98B.firstname.lastname@example.org>
Diego Novillo <email@example.com> writes:
| Mark Mitchell wrote on 01/01/07 14:46:
| > What a thread this has turned out to be.
| In general, I'm not too thrilled with the idea of disabling
| transformations for the sake of non-conforming code. However, I would
| not mind a -fconforming flag similar to -fstrict-aliasing.
Yes, we need a flag of some sort.
However, a C implementation with LIA-1 semantics is just as conforming
and standard as a C implementation without it. So, we must be careful
about what we hide behind the flags and what we want it to convey.