Closed Bug 708303 Opened 8 years ago Closed 8 years ago

Use pinReg/unpinReg more in write barriers

Categories

(Core :: JavaScript Engine, defect)

defect
Not set

Tracking

()

RESOLVED FIXED
mozilla12

People

(Reporter: billm, Assigned: billm)

References

Details

Attachments

(1 file, 2 obsolete files)

Attached patch patch (obsolete) — Splinter Review
Now that pinReg works with syncFancy, we can use it throughout the write barrier code.

This patch fixes one case that was previously broken, and it removes some unnecessary save/restore code in another place.

I'm a little worried about pinning two registers at once.
Attachment #579736 - Flags: review?(dmandelin)
Comment on attachment 579736 [details] [diff] [review]
patch

Review of attachment 579736 [details] [diff] [review]:
-----------------------------------------------------------------

I think pinning 2 is OK. The pin code is simple enough and shouldn't have any problems. I rechecked the reg allocator in ImmutableSync, and if all else fails, it can pick a last resort register, which just has to be in the standard set and not pinned.
Attachment #579736 - Flags: review?(dmandelin) → review+
Assignee: general → wmccloskey
Backed out. This fails with --jitflags=amdn.

https://hg.mozilla.org/integration/mozilla-inbound/rev/3fb1a1208df6
Target Milestone: mozilla11 → ---
Attached patch patch v2 (obsolete) — Splinter Review
The original patch was wrong because it was calling pinReg on registers that were not owned by the FrameState. This happened in two places:
1. In jsop_setelem_dense, where pinReg was called on a register that is sometimes obtained from tempRegForData (this one is safe) and sometimes from allocReg (no safe)
2. In jsop_setprop, where pinReg was called on a register obtained by allocReg

For the first problem, since we already save the register in question in VMFrame::scratch, I just restored the saved value when pinReg can't be used. pinReg is still used when the register comes from tempRegForData.

In the second problem, the register was already being allocated from SavedRegs. So I changed syncFancy so that it shouldn't clobber registers from SavedRegs. This further limits the set of registers available to syncFancy, but I suspect this should still be safe.
Attachment #579736 - Attachment is obsolete: true
Attachment #584848 - Flags: review?(dmandelin)
Attachment #584848 - Flags: review?(dmandelin) → review+
https://hg.mozilla.org/mozilla-central/rev/60eb0da71cdb
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
I backed this patch out as a suspected cause of a major new crash on mobile:
https://hg.mozilla.org/mozilla-central/rev/79e5d0b77d10

See bug 718765
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Depends on: 718765
Attached patch patch v3Splinter Review
Marty ran into this problem in bug 718852, which is probably the same thing as was happening with the Spiegel site: ARM only has three temp registers, and we had them all pinned. So there was nothing left for syncFancy to use.

This patch is more conservative. There was only one place where I wanted syncFancy to avoid using a SavedReg. So instead I changed that place to reload the register after the sync. It's a little hackier, but at this point I think that's what's called for.
Attachment #584848 - Attachment is obsolete: true
Attachment #591661 - Flags: review?(dmandelin)
Attachment #591661 - Flags: review?(dmandelin) → review+
https://hg.mozilla.org/mozilla-central/rev/9b81bf7d458c
Status: REOPENED → RESOLVED
Closed: 8 years ago8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.