Closed Bug 1618917 Opened 6 years ago Closed 6 years ago

Use default alias analysis GetObject semantics for some opcodes

Categories

(Core :: JavaScript Engine: JIT, task)

task
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla75
Tracking Status
firefox75 --- fixed

People

(Reporter: anba, Assigned: anba)

Details

Attachments

(4 files)

Some potential clean-ups noticed while working on bug 1614704.

These three opcodes don't override getAliasSet(), so it's better to let the
default case handle them, because then we can assert the alias information is
correct in debug builds.

Depends on D64777

Similar to part 3, it seems better to get the debug check for MCompare for
free. Also this make MCompare more similar to other opcodes like MToString,
MBitNot, and MBinaryBitwiseInstruction, which all three either have a "none"
alias-set or the default "store-any" alias-set.

Depends on D64778

Pushed by ccoroiu@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/40a351c7e4b1 Part 1: Use AliasSet::isNone() instead of testing isLoad() and isStore() separately. r=jandem https://hg.mozilla.org/integration/autoland/rev/3d690e518780 Part 2: Remove MArrayJoin::getAliasSet because it matches the default alias set. r=jandem https://hg.mozilla.org/integration/autoland/rev/f83f504514b6 Part 3: Fall through to the default case when getAliasSet() isn't overriden. r=jandem https://hg.mozilla.org/integration/autoland/rev/ce635c0f44ec Part 4: Handle MCompare in the default case. r=jandem
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: