On Mon, 2010-11-01 at 15:59 -0400, Gaetan Nadon wrote: > > 1) It is *NOT* a warning flag. Using CWARNFLAGS should *only* > > enable warnings, not change the resulting assembly. > > > > 2) It was never intended to be in all of the modules. It landed > > there by accident when the code was copy/pasted from one > > configure.ac to another and then into util-macros. > > > > 3) Performance gains are not in consideration here. > > > > I totally agree, but it does not justify simply removing the offending > flag as if it had never existed. It does have an impact on the > binaries, some modules need it, other don't, but we don't know which > ones for sure. That's my understanding, I could be wrong. >
Sorry I missed your latest post, came late. I'll get back to you. Thanks
signature.asc
Description: This is a digitally signed message part
_______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
