1 |
On Friday, July 02, 2010 16:39:57 Ryan Hill wrote: |
2 |
> On Fri, 2 Jul 2010 15:29:44 +0200 (CEST) Vaeth wrote: |
3 |
> > Ryan Hill wrote: |
4 |
> > > If your build system sets -ffast-math or -fstrict-aliasing |
5 |
> > > then the user can disable this by setting -fno-fast-math |
6 |
> > > or -fno-strict-aliasing in their CFLAGS. |
7 |
> > |
8 |
> > Just because some flags have "counter"-flags by accident, |
9 |
> > this does not hold for all flags. It is more reasonable to have |
10 |
> > other means that the flags are not modified in the first place. |
11 |
> |
12 |
> I can't think of any flags that don't have a corresponding counter flag, |
13 |
> other than -m flags. At least, all -f and -W flags have opposite -fno and |
14 |
> -Wno versions, even if they're not explicitly documented. |
15 |
|
16 |
and this isnt "by accident", this is in the fundamental design of gcc argument |
17 |
processing. the only -f/-W flags that lack this are rare exceptions. |
18 |
-mike |