Closed
Bug 699661
Opened 13 years ago
Closed 13 years ago
Make obj->getElement actually call into the ops getElement hooks
Categories
(Core :: JavaScript Engine, defect, P2)
Tracking
()
RESOLVED
FIXED
mozilla10
People
(Reporter: bzbarsky, Assigned: bzbarsky)
Details
Attachments
(1 file)
2.07 KB,
patch
|
Waldo
:
review+
|
Details | Diff | Splinter Review |
Should help with arrays of various sorts.
Assignee | ||
Comment 1•13 years ago
|
||
Attachment #571849 -
Flags: review?(jwalden+bmo)
Comment 2•13 years ago
|
||
(In reply to Boris Zbarsky (:bz) from comment #0) > Should help with arrays of various sorts. Help what? That's a pretty terse description. ;-) Is this just a bug in the way we use ops?
Comment 3•13 years ago
|
||
Comment on attachment 571849 [details] [diff] [review] Call the class getElement hook from JSObject::getElement as needed. Review of attachment 571849 [details] [diff] [review]: ----------------------------------------------------------------- Did I really write that, and forget to start calling the getElement op? Anybody need some fresh egg? Slightly-used, but still fresh?
Attachment #571849 -
Flags: review?(jwalden+bmo) → review+
Assignee | ||
Comment 4•13 years ago
|
||
> Help what?
Performance, sorry. Instead of converting uint32 to jsid and then calling the jsid ops and then checking to see whether the jsid is an int and branching on that, etc, this patch just directly calls the op taking a uint32, which arraylikes tend to fast-path.
Assignee | ||
Comment 5•13 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/ce40bde00ef8
Flags: in-testsuite-
Priority: -- → P2
Target Milestone: --- → mozilla10
Comment 6•13 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/ce40bde00ef8
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•