On Saturday 09 June 2007 22:59:54 Ryan Hill wrote: > Building ftjam with GCC 4.2 using -O2 optimizations fails with a > segfault in jam0. This is caused by a violation of strict-aliasing > rules which GCC 4.2 assumes are followed with optimization levels of -O2 > and above. It can be worked around with -fno-strict-aliasing. All jam > implementations appear to be affected, including Perforce jam, ftjam, > and Boost.Jam.
You should note that gcc 4.2 has an ugly strict aliasing bug in itself [0]. Not sure if the jam case is related though. [0] http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30252 -- Perfect is the enemy of good
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel
