Closed Bug 1586030 Opened 5 years ago Closed 5 years ago

BytecodeIterator post-increment operator is wrong

Categories

(Core :: JavaScript Engine, task, P3)

task

Tracking

()

RESOLVED FIXED
mozilla72
Tracking Status
firefox72 --- fixed

People

(Reporter: mgaudet, Assigned: asorholm)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Looking at the implementation of pre- and post-increment in BytecodeIterator, they have the same implementation... which means one of them is wrong.

I am pretty sure it's the post-increment.

To finish this bug we'll need to

  1. Fix the implementation
  2. Normally we'd have to audit the uses, but I don't see any currently.

I am going to set this as blocking Bug 1572504, because we'll need to make sure it doesn't use post increment unless we have fixed it.

Post-increment overload operator for BytecodeIterator class matches the
operator for pre-increment in BytecodeIterator, meaning the implementation of
post-increment is incorrect.

Assignee: nobody → asorholm
Status: NEW → ASSIGNED

(In reply to Matthew Gaudet (he/him) [:mgaudet] from comment #0)

Any suggestions on methods for testing the change? I guess I could use the increment operators in bug 1572504, but I would worry it would be difficult to untangle problems with the post-increment fix from problems with the patch for bug 1572504.

Priority: -- → P3
Keywords: checkin-needed
Pushed by nbeleuzu@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1613ca5b96c8 Fixed BytecodeIterator post-increment operator. r=mgaudet
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla72
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: