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