Closed
Bug 1832378
Opened 2 years ago
Closed 2 years ago
Refactor feature logic and don't require function references flag for enabling gc
Categories
(Core :: JavaScript: WebAssembly, task, P3)
Core
JavaScript: WebAssembly
Tracking
()
RESOLVED
FIXED
117 Branch
Tracking | Status | |
---|---|---|
firefox117 | --- | fixed |
People
(Reporter: rhunt, Assigned: rhunt)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
No description provided.
Assignee | ||
Comment 1•2 years ago
|
||
This commit cleans up some of our feature logic.
- A WasmFeatures.h internal header is added for all this code
- The stage of a feature is turned into an enum, not a separate
macro. This is generally easier to read.
As an improvement the concept of 'force enable flag' extension point
was added. This is used to enable the GC proposal even if the function
references proposal is not enabled.
This commit also lets wasm-gc/fr start building in beta/release. They
will remain off by default though (behind a pref).
Comment 2•2 years ago
|
||
There is an r+ patch which didn't land and no activity in this bug for 2 weeks.
:rhunt, could you have a look please?
If you still have some work to do, you can add an action "Plan Changes" in Phabricator.
For more information, please visit BugBot documentation.
Flags: needinfo?(ydelendik)
Flags: needinfo?(rhunt)
Assignee | ||
Updated•2 years ago
|
Flags: needinfo?(ydelendik)
Flags: needinfo?(rhunt)
Updated•2 years ago
|
Attachment #9332937 -
Attachment description: Bug 1832378 - wasm: Refactor feature flags. r?yury → Bug 1832378 - wasm: Refactor feature flags and let GC build in beta/release but remain disabled by-default. r?yury
Pushed by rhunt@eqrion.net:
https://hg.mozilla.org/integration/autoland/rev/8a8e8ec667ea
wasm: Refactor feature flags and let GC build in beta/release but remain disabled by-default. r=yury
Comment 5•2 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox117:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 117 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•