Closed
Bug 727741
Opened 13 years ago
Closed 13 years ago
IonMonkey: arguments.length is incorrect when padding missing arguments
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
DUPLICATE
of bug 749822
People
(Reporter: jandem, Unassigned)
References
Details
Attachments
(1 file)
(deleted),
patch
|
Details | Diff | Splinter Review |
The following testcase fails with --ion -n:
--
function f(x, y) {
assertEq(arguments.length, 0);
}
for (var i = 0; i < 50; i++)
f();
--
test.js:1: Error: Assertion failed: got 2, expected 0
This causes some jit-test failures with --ion-eager -n.
Comment 1•13 years ago
|
||
So the problem is that we pad the arguments, but nowhere we keep around the information on how much of the provided arguments are real. This fixes that, but I don't really know if that's the only place we need to lie to make that optimization work correctly eg. after bailing out and rebuilding the frame.
Comment 2•13 years ago
|
||
Learned of this bug's existence a bit too late. Augh!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•