Closed Bug 1643669 Opened 5 years ago Closed 5 years ago

Warp: Assertion failure: def->type() == MIRType::Int32 || def->type() == MIRType::Double in MTypedArrayIndexToInt32

Categories

(Core :: JavaScript Engine: JIT, defect, P3)

defect

Tracking

()

RESOLVED FIXED
mozilla79
Tracking Status
firefox79 --- fixed

People

(Reporter: anba, Assigned: evilpies)

References

Details

Attachments

(1 file)

Run with --ion-offthread-compile=off --warp:

function f(ta, i) {
    return ta[i];
}

var ta = new Int32Array(10);
var xs = [0, 1, 2, -1];

for (var i = 0; i < 100_000; ++i) {
    f(ta, xs[i&3]);
}

Asserts with:

Assertion failure: def->type() == MIRType::Int32 || def->type() == MIRType::Double, at /home/andre/git/mozilla-central/js/src/jit/MIR.h:7332

Is this just a bogus assert for Warp?

Flags: needinfo?(evilpies)

I think so. MTypedArrayIndexToInt32 has a type policy for unboxing int32/double so it should be fine.

Flags: needinfo?(evilpies)
Severity: -- → S4
Priority: -- → P3
Assignee: nobody → evilpies
Pushed by evilpies@gmail.com: https://hg.mozilla.org/integration/autoland/rev/6fbdf96ceeb6 Correct input type for MTypedArrayIndexToInt32 in Warp. r=jandem
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla79
Regressions: 1647114
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: