gecko-dev/js
Jan de Mooij daa9fa5186 Bug 1782188 - Use more reliable endStackAddress when profiling JIT/Wasm frames. r=iain
We were using the activation's exitFP for this, but that value isn't cleared
when we return to JIT code from C++ so we could use stale values if we're in JIT
code (or used `callWithABI` calls without an exit frame). This could result in
unsymbolicated frames or missing frames in profiles.

This patch changes the JIT and Wasm frame iterators to set `endStackAddress` from
their constructor. In the outer iterator we then keep track of the first value for
the current activation and use that instead of the activation's exitFP.

Adds an assertion to the single-step callback to check `frame.endStackAddress >= state.sp`
in simulator builds. This failed on many jit-tests before this patch and passes now.

Differential Revision: https://phabricator.services.mozilla.com/D153214
2022-08-01 11:10:52 +00:00
..
ductwork/debugger Bug 1667455 - Part 6: Stop importing Services.jsm from chrome-priv JS code, non-top-level or multi-line cases. r=kmag,perftest-reviewers,AlexandruIonescu,sparky 2022-07-11 12:41:51 +00:00
examples
loader Bug 1781124 - Use static pref for dom.importMaps.enabled in module loader. r=allstarschh 2022-07-26 06:30:46 +00:00
public Bug 1782188 - Use more reliable endStackAddress when profiling JIT/Wasm frames. r=iain 2022-08-01 11:10:52 +00:00
src Bug 1782188 - Use more reliable endStackAddress when profiling JIT/Wasm frames. r=iain 2022-08-01 11:10:52 +00:00
xpconnect Bug 1781425 - wasm: Remove baldrdash. r=jseward,supply-chain-reviewers 2022-07-27 22:30:17 +00:00
app.mozbuild
ffi.configure
moz.build
moz.configure Bug 1781425 - wasm: Remove baldrdash. r=jseward,supply-chain-reviewers 2022-07-27 22:30:17 +00:00
sub.configure