Comment #7 on issue 266 by craig.schlenter: Fix strict aliasing problems in
v8/src/third_party/dtoa/dtoa.c
http://code.google.com/p/v8/issues/detail?id=266
Progress!! #define NO_HEX_FP fixes the parse-int-float test for me.
The line in parse-int-float.js that was unhappy was:
assertEquals(0, parseFloat('0x12'));
and so the "Failure: expected <0> found <18>"
makes perfect sense in the context of whether dtoa.c has hex float parsing
enabled or
not.
I'll update the patch tonight...
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
-~----------~----~----~----~------~----~------~--~---
