Closed
Bug 478197
Opened 16 years ago
Closed 16 years ago
[interpreter] int increment/decrement operators buggy
Categories
(Tamarin Graveyard :: Virtual Machine, defect, P2)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
flash10.1
People
(Reporter: lhansen, Assigned: lhansen)
Details
Attachments
(1 file, 2 obsolete files)
2.44 KB,
text/plain
|
Details |
If the representation of the number is a double they add/subtract 1.0 and go on their merry way, but they should truncate.
Assignee | ||
Comment 1•16 years ago
|
||
The patch is considered preliminary. It needs a test case, which needs to be constructed with the assembler to be somewhat reliable.
Assignee: nobody → lhansen
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•16 years ago
|
||
Requires a simple harness that I'm not including here. Run with -Dinterp to show that it's not working in the interpreter. (The test case also demonstrates that the offered patch is not correct.)
Attachment #361973 -
Attachment is obsolete: true
Assignee | ||
Comment 3•16 years ago
|
||
Proper test cases for both increment and decrement that fit into the assembler test harness. The change to the 'I' tests splits those tests so that they can be run both interpreted and jitted (the jitter would fail on the existing tests because the function was too large).
Attachment #363316 -
Attachment is obsolete: true
Assignee | ||
Comment 4•16 years ago
|
||
Ed, the decrement_i and declocal_i tests fail in the jit too, maybe you want to take a look at the test cases to make sure I've not done something silly.
Comment 5•16 years ago
|
||
decrement_i is squirrely -- I've queued a buildbot run that has decrement_i tests enabled. I'll report results.
Comment 6•16 years ago
|
||
[th reminds self to use ISO English]
decrement_i yields inconsistent results on different platforms.
Updated•16 years ago
|
Updated•16 years ago
|
Assignee | ||
Updated•16 years ago
|
Priority: -- → P2
Assignee | ||
Comment 7•16 years ago
|
||
The increment problem has gone away. The test cases for decrement were incorrect.
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Updated•15 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•