Don't transpile stubs with popped fuses.
Categories
(Core :: JavaScript Engine: JIT, task, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox143 | --- | fixed |
People
(Reporter: mgaudet, Assigned: jandem)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
In principle, we could have a monomorphic stub with a guard fuse where the fuse pops before we transpile it; might be nice to detect this and skip transpilation of these stubs.
This is reasonably unlikely, but perhaps still worth it?
| Assignee | ||
Comment 1•1 year ago
|
||
There are a few places where we manually scan CacheIR ops and read their arguments.
In this case the reader calls have to match the arguments in the YAML file and this
can be error-prone.
The next patch will add another place where we do this so this patch adds code generation
to make this more ergonomic.
For PBL this patch converts a few interesting ops but doesn't convert all of them yet.
Updated•1 year ago
|
| Assignee | ||
Comment 2•1 year ago
|
||
Move the dependency tracking from the transpiler to WarpOracle and use a bailout
instead of transpiling the stub if we have a popped fuse. This avoids finishing
an Ion compilation and then immediately throwing away the result when we check
the fuse dependencies at the end.
This likely doesn't matter a lot for the current fuses, but becomes more important with
object property fuses.
https://hg.mozilla.org/mozilla-central/rev/f8657413e8a3
https://hg.mozilla.org/mozilla-central/rev/088251a88b60
Updated•1 year ago
|
Description
•