Closed
Bug 566076
Opened 15 years ago
Closed 13 years ago
Don't initialize fslots on allocation.
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: gal, Unassigned)
References
Details
Attachments
(1 file)
|
22.53 KB,
patch
|
Details | Diff | Splinter Review |
This saves a bunch of branching and initializing effort during allocation. It will be even more critical if objects grow to 16 words.
|
Reporter | |
Comment 1•15 years ago
|
||
Also, slots are now initialized to NULL, not VOID. Faster to memset.
Assignee: general → gal
|
|
Reporter | |
Comment 2•14 years ago
|
||
This patch is too broadly scoped and should be split up. Will discuss with paul.
|
|
Reporter | |
Updated•14 years ago
|
Summary: Clear objects during GC, don't initialize fslots on allocation. → Don't initialize fslots on allocation.
|
||
Updated•14 years ago
|
|
||
Updated•13 years ago
|
Assignee: paul.biggar → general
|
||
Comment 3•13 years ago
|
||
At this point, is this a WONTFIX?
|
||
Comment 4•13 years ago
|
||
Yeah. The slots code has been overhauled massively. Wouldn't surprise me if this was already done.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•