Closed
Bug 981257
Opened 11 years ago
Closed 10 years ago
We're running out of node bits
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
FIXED
mozilla34
People
(Reporter: bzbarsky, Assigned: Ms2ger)
References
(Depends on 1 open bug)
Details
Attachments
(1 file)
3.19 KB,
patch
|
bzbarsky
:
review+
|
Details | Diff | Splinter Review |
We have two bool bits left, and only one non-bool bit. That's not counting the event state, which we have 18 free bits in, if we want to try using them somehow, of course.
Looking at our existing bits, we can nix ParentIsContent and replace its one use with:
nsIContent* GetParent() const {
return mParent && mParent->IsContent() ? mParent : nullptr;
}
That does mean reading stuff from the parent, which may mean more cache misse, but the caller was probably going to anyway. Worth doing that?
Any other bits we can obviously kill off?
Or should I just not be worrying about this until the next poor sod tries to add flags and gets compile errors?
Killing XBL would free up several ...
Is directionality important enough to chew up two of them?
NODE_ATTACH_BINDING_ON_POSTCREATE appears to be unused. That's almost too good to be true.
Reporter | ||
Comment 2•11 years ago
|
||
> Killing XBL would free up several ...
Yes, but that's not a short-term project.
> Is directionality important enough to chew up two of them?
Directionality uses two non-boolean flags and 6 boolean flags. I couldn't find obvious ways to nix some of them. :(
> NODE_ATTACH_BINDING_ON_POSTCREATE appears to be unused.
Oho! It is in fact unused. It went away in bug 883892. We used to set the flag in PreCreate (because we had to check for XBL there to decide whether we can do slimwrappers) and check it in PostCreate (to avoid redoing all that checking work), but now Element::WrapObject just does all the work involved, so there's no need to smuggle state along.
Assignee | ||
Comment 3•11 years ago
|
||
Attachment #8388060 -
Flags: review?(khuey)
Comment on attachment 8388060 [details] [diff] [review]
Patch v1
I would prefer that bz reviewed this, mostly because I'm not sure if there's anywhere else that depends on the numbers involved here.
Attachment #8388060 -
Flags: review?(khuey) → review?(bzbarsky)
Reporter | ||
Comment 5•11 years ago
|
||
Comment on attachment 8388060 [details] [diff] [review]
Patch v1
This should be good. r=me
Attachment #8388060 -
Flags: review?(bzbarsky) → review+
Can we wait to land it until I'm ready to land bug 996796?
Blocks: 996796
Reporter | ||
Comment 8•11 years ago
|
||
Sure. You're the main consumer for this patch right now!
Assignee | ||
Comment 9•11 years ago
|
||
I forgot about this... Let me know when/if I should land it.
Flags: needinfo?(Ms2ger)
Assignee: nobody → Ms2ger
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla34
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
•