Differential output with --ion-eager
Categories
(Core :: JavaScript Engine: JIT, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox102 | --- | affected |
People
(Reporter: decoder, Unassigned)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression, testcase, Whiteboard: [bugmon:update,bisect])
Attachments
(1 file)
379 bytes,
text/plain
|
Details |
The following testcase produces different outputs on mozilla-central revision 20220512-2f240882d907 (debug build):
function testMathyFunction(f, inputs) {
var results = [];
for (var j = 0; j < inputs.length; ++j)
for (var k = 0; k < inputs.length; ++k)
results.push(f(inputs[j], inputs[k]));
print(results);
}
mathy5 = (
function(x, y) {
return (+(x || Math.fround()) ? (+y) : (+Math.log()))
}
);
testMathyFunction(mathy5, [0, -0, '', '\0', [], undefined])
Run with --fuzzing-safe --differential-testing --ion-offthread-compile=off --ion-eager:
NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,0,0,0,NaN,0,NaN,0,0,0,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN
Run with --fuzzing-safe --differential-testing --ion-offthread-compile=off:
NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN,NaN
JIT bug, marking s-s until investigated.
Reporter | ||
Comment 1•3 years ago
|
||
Comment 2•3 years ago
|
||
This sounds like a type policy issue on Fround, which change the way we evaluate the condition.
But this might not be the only issue as I would expect to see the patterns of 0 and NaN to be repeated. So there is possibly an issue with +y
as well.
Updated•3 years ago
|
Comment 3•3 years ago
|
||
Bugmon Analysis
Unable to reproduce bug 1769209 using build mozilla-central 20220512094957-2f240882d907. Without a baseline, bugmon is unable to analyze this bug.
Removing bugmon keyword as no further action possible. Please review the bug and re-add the keyword for further analysis.
Comment 4•3 years ago
|
||
Nicolas: is lowering the severity to S3 an indicator that you don't think this is exploitable?
Comment 5•3 years ago
|
||
This is a duplicate of bug 1769723.
Comment 6•3 years ago
|
||
(In reply to Daniel Veditz [:dveditz] from comment #4)
Nicolas: is lowering the severity to S3 an indicator that you don't think this is exploitable?
I reduced it to S3, as we have a toggle to disable Ion. Then whether this is a satisfactory work-around is debatable.
Updated•3 years ago
|
Description
•