On Sat, Jun 17, 2006 at 03:35:10PM +0200, Harald van D??k wrote: > On Sat, Jun 17, 2006 at 03:32:36PM +0200, Kevin F. Quinn wrote: > > Easiest way to find these is to stick -Wall in global CFLAGS (or just > > -Wstrict-aliasing if you want to be more specific), and grep the build > > log for 'will break strict aliasing' (LC_ALL=C obviously).
http://dev.gentoo.org/~pvdabeel/strict-aliasing.log It seems that roughly 10% of the ebuilds tested with strict-aliasing in cflags warn about type punned pointers breaking strict aliasing rules. A few ebuilds did not make it through testing with strict aliasing, but did with -fno-strict-aliasing. Those should be obvious candidates for appending the fno-strict-aliasing flag (or an attempt at fixing the violation by patching the code). > That warning is given for valid code too. Please only add > -fno-strict-aliasing if you actually find a package misbehaves without > it, or if you have verified that there is indeed an aliasing violation > in the code. Right now we have -fno-strict-aliasing in the default cflags and are considering auditing the tree for aliasing violations. Pieter Van den Abeele > -- > gentoo-dev@gentoo.org mailing list -- gentoo-dev@gentoo.org mailing list
