• Frank Tang's avatar
    [Temporal] Use double/int32_t instead of int64_t for duration parsing · a165e82e
    Frank Tang authored
    Use double instead of int64_t and int32_t in duration parsing result
    so we can parse very large duration fields as infinity and throw RangeError in later stages. The three fractional parts can hold up value from 0 to 999,999,999 so we use int32_t to hold it. Other part could be infinity so we use double to hold it. Also rearrange the order of the three int32_t in the struct ParsedISO8601Duration after all the double
    
    Bug: v8:11544
    Change-Id: I7e5b02f7c7bbb60997f1419f016aed61dd3e0d6c
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3840761Reviewed-by: 's avatarShu-yu Guo <syg@chromium.org>
    Commit-Queue: Frank Tang <ftang@chromium.org>
    Cr-Commit-Position: refs/heads/main@{#82754}
    a165e82e
Name
Last commit
Last update
..
local-tests/test Loading commit data...
BUILD.gn Loading commit data...
OWNERS Loading commit data...
README Loading commit data...
detachArrayBuffer.js Loading commit data...
harness-adapt-donotevaluate.js Loading commit data...
harness-adapt.js Loading commit data...
harness-agent.js Loading commit data...
harness-ishtmldda.js Loading commit data...
prune-local-tests.sh Loading commit data...
test262.status Loading commit data...
testcfg.py Loading commit data...
upstream-local-tests.sh Loading commit data...