Closed
Bug 1508085
Opened 6 years ago
Closed 6 years ago
Track the sizes of commonly used node types also in 32 bit builds
Categories
(Core :: DOM: Core & HTML, enhancement)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla65
Tracking | Status | |
---|---|---|
firefox65 | --- | fixed |
People
(Reporter: smaug, Assigned: smaug)
References
Details
Attachments
(1 file)
3.12 KB,
patch
|
ehsan.akhgari
:
review+
|
Details | Diff | Splinter Review |
I need some more bits on nsINode, but better to ensure we don't increase the sizes of commonly used node types accidentally.
EXTRA_DOM_NODE_BYTES is 8 even on 32bit just to be safe with different alignments.
It affects anyhow only debug builds.
Right now on 64bit nsINode has 4 bytes for use without any change to sizes.
On 32bit if one wants 4 bytes on Element, mAttrs need to move from FragmentOrElement to Element (which makes sense anyhow). That way alignment is
better and 4 bytes on nsINode can be used for flags and still keeping Element size <= 80.
But Text is trickiest. It is using 64 bytes on 32bit. But then, Text nodes don't use mChildCount or mFirstChild for anything.
https://treeherder.mozilla.org/#/jobs?repo=try&revision=6a8ba68490e7d63d6a9c9168e61cd8435d4b8d63
Assignee | ||
Comment 1•6 years ago
|
||
Attachment #9025898 -
Flags: review?(ehsan)
Updated•6 years ago
|
Attachment #9025898 -
Flags: review?(ehsan) → review+
Pushed by opettay@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/9cdaafe18302
Track the sizes of commonly used node types also in 32 bit builds, r=ehsan
Comment 4•6 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox65:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla65
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•