(In reply to Ryan Hunt [:rhunt] from comment #4) > Ah, this is probably a bug in our integration with the profiler in the new lazy tiering system. We don't report the correct tier here [1]. > > I'll see if I can write a quick patch to fix this. > > [1] https://searchfox.org/mozilla-central/rev/6597dd03bad82c891d084eed25cafd0c85fb333e/js/src/wasm/WasmCode.cpp#1384 Note that I have updated comment 0 with profiles of lazy tiering disabled and enabled. In both cases, the profiler shows WASM(Baseline).
Bug 1933997 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Ryan Hunt [:rhunt] from comment #4) > Ah, this is probably a bug in our integration with the profiler in the new lazy tiering system. We don't report the correct tier here [1]. > > I'll see if I can write a quick patch to fix this. > > [1] https://searchfox.org/mozilla-central/rev/6597dd03bad82c891d084eed25cafd0c85fb333e/js/src/wasm/WasmCode.cpp#1384 Note that I have updated comment 0 with profiles of lazy tiering disabled and enabled. In both cases, the profiler shows WASM(Baseline). Additionally, in the lazy tier enabled profile, a lot of the time on the content-process mainthread is shown as WASM(Other).