Jan de Mooij 6828c4dbf4 Bug 1776358 - Only include wasmMaxStackArgBytes in Ion frame size if there are calls. r=rhunt ... Because `wasmMaxStackArgBytes` is calculated early on, it was possible we later eliminated all call instructions and `needsStaticStackAlignment` was false, but we still included `wasmMaxStackArgBytes` in the frame size, breaking stack alignment invariants on ARM64. The simplest fix is to not include `wasmMaxStackArgBytes` if we know there are no calls (left). This fixes an old Ion ARM64 bug exposed by the assertion added in bug 1774449. Differential Revision: https://phabricator.services.mozilla.com/D150244		2022-06-25 14:02:55 +00:00
..
ductwork/debugger	Bug 1765167 - Part 5: Stop using Cu.import in js/. r=mossop	2022-05-03 06:32:30 +00:00
examples
loader	Bug 1769322 - Allow for the possibility of non-xpc globals in nsIGlobal::IsScriptForbidden r=smaug	2022-05-24 17:23:32 +00:00
public	Bug 1774796 - Add largest-first delazification strategy. r=arai	2022-06-20 13:33:49 +00:00
src	Bug 1776358 - Only include wasmMaxStackArgBytes in Ion frame size if there are calls. r=rhunt	2022-06-25 14:02:55 +00:00
xpconnect	Backed out changeset 004885c1597c (bug 1775150)for causing bustage on mozJSModuleLoader.h. CLOSED TREE	2022-06-25 16:59:21 +03:00
app.mozbuild
ffi.configure
moz.build
moz.configure	Bug 1766986 - wasm: Remove last ENABLE_WASM_EXCEPTIONS ifdefs. r=yury	2022-06-17 15:33:10 +00:00
sub.configure