Generalize priority support in the IPDL compiler
Categories
(Core :: IPC, task, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox110 | --- | fixed |
People
(Reporter: mccr8, Assigned: mccr8)
References
Details
Attachments
(1 file)
We have a ton of priorities in IPDL now. It might be worth generalizing things instead of having little bits of boilerplate scattered around. I'm imagining an array of pairs, where the first part of the pair is the IPDL name and the second part is the C++ name. The internal enum value would be an index into the array.
Comment 1•3 years ago
|
||
There was some discussion on Matrix and it was pointed out that priority is currently a 3-bit field, so this will need a little subtlety if we want to add more than 3 new priorities (+ the current 5).
| Assignee | ||
Comment 2•3 years ago
|
||
I was mostly thinking about the representation of priority values in the IPDL compiler itself, but that's good to keep in mind.
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Comment 3•3 years ago
|
||
This patch makes it so that you only need to add a new element to a list
to add a new priority to the IPDL compiler.
| Assignee | ||
Comment 4•3 years ago
|
||
A similar thing could be done for the nested attributes, but hopefully nobody is clamoring to add lots more of those.
Comment 6•3 years ago
|
||
| bugherder | ||
Description
•