Allow disabling constant pools in AssemblerBufferWithConstantPools
Categories
(Core :: JavaScript Engine: JIT, task, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox154 | --- | fixed |
People
(Reporter: anba, Assigned: anba)
References
(Blocks 1 open bug)
Details
Attachments
(5 external files)
Allow disabling constant pools in AssemblerBufferWithConstantPools when only branch deadlines are needed, as is the case for riscv64.
| Assignee | ||
Comment 1•5 months ago
|
||
Spew the constant pool instructions in WritePoolGuard, because the guard
instruction is written after the veneer branches, even though the guard
appears earlier in the final assembly.
| Assignee | ||
Comment 2•5 months ago
|
||
Allow to opt-out of constant pools when setting HeaderSize to zero.
This will be used in part 3 for RISCV64.
| Assignee | ||
Comment 3•5 months ago
|
||
And remove functions which are no longer needed when not using constant pools.
| Assignee | ||
Comment 4•5 months ago
|
||
Shrinks the size from 160 to 152 bytes.
Drive-by change:
- Use field initialisers when possible.
| Assignee | ||
Comment 5•5 months ago
|
||
Updated•4 months ago
|
Backed out for causing build bustages at testAssemblerBuffer.cpp
Backout link
Push with failures
Failure log(s)
| Assignee | ||
Comment 9•4 months ago
|
||
MOZ_NO_UNIQUE_ADDRESS contains a note that [[no_unique_address]] should be used for C++20, but apparently Windows builds still require [[msvc::no_unique_address]]. Switching [[no_unique_address]] to MOZ_NO_UNIQUE_ADDRESS in part 2 fixes the build error.
Comment 10•4 months ago
|
||
Comment 11•4 months ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/ac9f2caa38c7
https://hg.mozilla.org/mozilla-central/rev/251adc40a3e9
https://hg.mozilla.org/mozilla-central/rev/e56426ef9221
https://hg.mozilla.org/mozilla-central/rev/961f7ec6c79a
https://hg.mozilla.org/mozilla-central/rev/79bfd02dfed2
Updated•3 months ago
|
Description
•