Closed Bug 913749 Opened 11 years ago Closed 11 years ago

Differential Testing: Different output message involving .length

Categories

(Core :: JavaScript Engine, defect)

x86_64
macOS
defect
Not set
major

Tracking

()

RESOLVED FIXED
mozilla26

People

(Reporter: gkw, Assigned: jandem)

Details

(Keywords: testcase)

Attachments

(1 file, 1 obsolete file)

try { y = Float32Array(11); x = new Array; Object.defineProperty(x, 18, { get: (function() { y.length; }), }); this(); } catch (e) {} try { y = undefined; } catch (e) {} try { print(x); } catch (e) {} try { print(x); } catch (e) {} prints nothing on js opt shell on m-c changeset 3697f962bb7b without any CLI arguments but prints: ,,,,,,,,,,,,,,,,,, with --ion-eager. My configure flags are: CC="clang -Qunused-arguments" AR=ar CXX="clang++ -Qunused-arguments" sh /Users/skywalker/Desktop/js-opt-64-dm-darwin-mozilla-central-146034-3697f962bb7b-oqFA2p/compilePath/js/src/configure --target=x86_64-apple-darwin11.4.0 --enable-optimize --disable-debug --enable-profiling --enable-gczeal --enable-debug-symbols --enable-methodjit --enable-type-inference --disable-tests --enable-more-deterministic --with-ccache
Flags: needinfo?(jdemooij)
Attached patch Patch (obsolete) (deleted) — Splinter Review
The problem is that we add MUnbox(MIRType_Object, Fallible) followed by MTypedArrayLength Then DCE eliminates these two instructions and we no longer bailout and throw an exception when the input is |undefined|. I think fallible unbox instructions should be marked as Guard. I will check benchmarks before landing this but I doubt it will matter.
Assignee: general → jdemooij
Status: NEW → ASSIGNED
Attachment #801520 - Flags: review?(hv1989)
Flags: needinfo?(jdemooij)
Severity: critical → major
Comment on attachment 801520 [details] [diff] [review] Patch Review of attachment 801520 [details] [diff] [review]: ----------------------------------------------------------------- I think this patch is reduced to a one-liner since revision bug 909717 landed.
Attachment #801520 - Flags: review?(hv1989)
Attached patch Patch (deleted) — Splinter Review
Rebased and it's indeed a one-liner now. Running some benchmarks now.
Attachment #801520 - Attachment is obsolete: true
Attachment #802972 - Flags: review?(hv1989)
The patch has no effect on SS/Kraken/Octane.
Comment on attachment 802972 [details] [diff] [review] Patch Review of attachment 802972 [details] [diff] [review]: ----------------------------------------------------------------- Seems fine for me, since we don't have a regression. It might be worthwhile for the future to remove the guard annotation on Unbox[Fallible] if we see that DCE its scope is limited by it. In that case we will need to use TypeBarrier/MGuardObject for these cases. For now it's a bit too tedious to find all cases where we should use Unbox[Fallible] that might get removed and TypeBarrier/MGuardObject that can't get removed.
Attachment #802972 - Flags: review?(hv1989) → review+
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla26
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: