Closed Bug 725357 Opened 12 years ago Closed 12 years ago

IonMonkey: Don't call TypeScript::Monitor from the GetElement stub

Categories

(Core :: JavaScript Engine, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla13

People

(Reporter: jandem, Assigned: jandem)

References

(Blocks 1 open bug)

Details

(Whiteboard: [Leave open after merge])

Attachments

(1 file, 2 obsolete files)

Attached patch Patch (obsolete) — Splinter Review
I think you suggested this a while ago and this is a nice speedup, also because getting the script and pc is more expensive for Ion frames.
Attachment #595418 - Flags: review?(bhackett1024)
Comment on attachment 595418 [details] [diff] [review]
Patch

Brian says we need to emit code after the GetElement call to handle the monitoring, since barriers don't handle this. I somehow missed the code for this in JM (testPushedType)..
Attachment #595418 - Flags: review?(bhackett1024)
Attached patch Patch (obsolete) — Splinter Review
Attachment #595418 - Attachment is obsolete: true
Attachment #595503 - Flags: review?(dvander)
Attached patch PatchSplinter Review
A bit cleaner than the previous patch and now also checks the result of the GETPROP/NAME VM calls (fixes bug 728187 and tons of inference failures caught by the fuzzers).

I can land the jsinterp* changes on inbound first.
Attachment #595503 - Attachment is obsolete: true
Attachment #595503 - Flags: review?(dvander)
Attachment #598566 - Flags: review?(dvander)
Attachment #598566 - Flags: review?(dvander) → review+
https://hg.mozilla.org/integration/mozilla-inbound/rev/b712e681cc8c

Please don't close this bug when merging to m-c.
Whiteboard: [Leave open after merge]
https://hg.mozilla.org/projects/ionmonkey/rev/eef8527f7ef1
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: