We have had an effort to try to make V8 work with strict aliasing on newer GCC versions, but this really conflicts with the way we handle heap objects. It has been an uphill battle as each time we make it work in some version of GCC it broke in the next, and locating the reason gets more complicated each time, so for the time being this has been postponed.
The reason for not turning strict aliasing off completely is that is actually gives some performance improvement on GCC versions prior to 4.4. The simple solution just setting the GCC_VERSION variable is used as nobody has added a more automatic detection mechanism to our SCons build. Regards, Søren On Fri, May 7, 2010 at 09:47, Stephan Beal <[email protected]> wrote: > 2010/5/7 Søren Gjesse <[email protected]> > > This is due to GCC 4.4 and strict aliasing. You will have to define the >> variable GCC_VERSION to 44 for the V8 SCons script to turn off strict >> aliasing when compiling. >> >> $ export GCC_VERSION=44 >> $ scons >> > > Just out of curiosity: > > a) Is this due to a bug in gcc (too pedantic?) or > questionable/non-conformant code in v8? > > b) can SConstruct be modified to "do the right thing" if it detects gcc? (i > despise python and, by extension, know nothing about hacking scons.) > > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > > -- > v8-users mailing list > [email protected] > http://groups.google.com/group/v8-users > -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
