Description[turbofan] Properly represent the float64 hole.
The hole NaN should also have proper Type::Hole, and not silently hide
in the Type::Number. This way we can remove all the special casing for
the hole NaN, and we also finally get the CheckNumber right.
This also allows us to remove some ducktape from the Deoptimizer, as for
escape analyzed FixedDoubleArrays we always pass the hole value now to
represent the actual holes.
Also-By: jarin@chromium.org
BUG=chromium:684208, chromium:709753, v8:5267
R=jarin@chromium.org
Review-Url: https://codereview.chromium.org/2814013003
Cr-Commit-Position: refs/heads/master@{#44603}
Committed: https://chromium.googlesource.com/v8/v8/+/8c0c5e8117a0c935d6f2e5f6e540674d46753a87
Patch Set 1 #Patch Set 2 : CheckNumber does not need a restriction type. #Patch Set 3 : Make sure the_hole has the correct hole NaN bit pattern on Win32. #
Total comments: 2
Messages
Total messages: 25 (14 generated)
|