This looks a lot like what I did when I tried to update the dtoa version
used in V8.

Unfortunately, gcc 4.2.4 has a problem with this version of dtoa when
using -O2 or above.  I get the following failure only in release mode
when using -O2 or above:

=== release number-tostring ===
Path: mjsunit/number-tostring
/home/ager/v8/v8/test/mjsunit/mjsunit.js:50: Failure: expected
<0.00000000000000000010> found <0.0000000000000000000:>

Therefore, I cannot put this patch in as is and we will have to compile
with -fno-strict-aliasing on gcc 4.4 for now.



http://codereview.chromium.org/115176

--~--~---------~--~----~------------~-------~--~----~
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to