Closed
Bug 742562
Opened 13 years ago
Closed 13 years ago
IonMonkey: Inline allocation for JSOP_NEWARRAY
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
People
(Reporter: sstangl, Assigned: sstangl)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
4.47 KB,
patch
|
dvander
:
review+
|
Details | Diff | Splinter Review |
JSOP_NEWOBJECT should use the MacroAssembler's getNewObject() path where possible. In terms of benchmarks, this mostly affects v8-splay; 3d-cube; and a few kraken tests, especially crypto-ccm.
|
Assignee | |
Comment 1•13 years ago
|
||
Ahem, that should have read JSOP_NEWARRAY.
|
|
Assignee | |
Updated•13 years ago
|
Assignee: general → sstangl
|
|
Assignee | |
Comment 2•13 years ago
|
||
Brings splay 125ms -> 112ms. Combined with JSOP_NEWOBJECT patch, splay goes from 125ms -> 82ms. 3d-cube goes from ~35ms to ~32ms, not a significant change.
Attachment #612418 -
Flags: review?(dvander)
|
||
Updated•13 years ago
|
Attachment #612418 -
Flags: review?(dvander) → review+
|
|
Assignee | |
Comment 3•13 years ago
|
||
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
•