This commit uses a regex to automatically switch
(block $label valtype ...
with
(block $label (result valtype ...
This should have been combined with the earlier 'block' commit, but was not
realised until too late.
Differential Revision: https://phabricator.services.mozilla.com/D67254
--HG--
extra : moz-landing-system : lando
This commit uses a regex to automatically switch
(loop valtype ...
with
(loop (result valtype ...
Differential Revision: https://phabricator.services.mozilla.com/D67253
--HG--
extra : moz-landing-system : lando
This commit uses a regex to automatically switch the export syntax for table.
Differential Revision: https://phabricator.services.mozilla.com/D67252
--HG--
extra : moz-landing-system : lando
This commit uses a regex to automatically switch the export syntax
for memory.
Differential Revision: https://phabricator.services.mozilla.com/D67251
--HG--
extra : moz-landing-system : lando
This commit uses a regex to automatically change exports of indices
to specify that they are exporting functions.
Differential Revision: https://phabricator.services.mozilla.com/D67250
--HG--
extra : moz-landing-system : lando
This commit uses a regex to automatically switch call_indirect type signature
immediates to use an explicit '(type $id)' wrapper.
This has a negative interaction with the gc/ tests which use an identifier
immediately after call_indirect to specify the table and not the signature. A
later commit fixes this.
Differential Revision: https://phabricator.services.mozilla.com/D67249
--HG--
extra : moz-landing-system : lando
This commit uses a regex to automatically replace uses of
if valtype
with
if (result valtype)
Differential Revision: https://phabricator.services.mozilla.com/D67248
--HG--
extra : moz-landing-system : lando
This commit uses a regex to automatically replace uses of
block valtype
with
block (result valtype)
Differential Revision: https://phabricator.services.mozilla.com/D67247
--HG--
extra : moz-landing-system : lando
This commit removes the old WasmTextToBinary implementation and replaces
it with a stub that calls into the rust wat implementation.
The old wasmTextToBinary function took an optional boolean parameter to
indicate that additional metadata was desired. This extra metadata was
a list of offsets of instructions in the code section. I'm not sure if
this was intentional or not, but it looks like it only includes root
expressions of nested s-exprs.
These offsets were used in two tests, debug/wasm-breakpoints.js and a
wasm/regress test. Adding this functionality into 'wat' proved to be a large
change for a function that didn't seem to have much use cases. A new
wasmCodeOffsets function was added to replicate this feature. It's implemented
in rust using the 'wasmparser' crate that cranelift uses. When cranelift is
compiled, this shouldn't result in an increased binary size. If the compile
time or binary size proves to be an issue in non-cranelift builds, I think
we can make this a conditional feature for JS-shells only.
Differential Revision: https://phabricator.services.mozilla.com/D67245
--HG--
extra : moz-landing-system : lando
There are cases when GV is being animated and it ends up being smaller than the
dynamic toolbar for a few frames. When that happens we really don't want to
crash and we can just ignore it.
Differential Revision: https://phabricator.services.mozilla.com/D67364
--HG--
extra : moz-landing-system : lando
This patch enables multi-value calls and returns, adding some tests, and
conditionally disabling a couple expect-fail reftests that now pass.
It also changes to make calling multi-result WebAssembly functions from
JavaScript raise a run-time error, and likewise for calling out to
multi-result JS function from wasm. Previously these would abort at
stub generation time.
Differential Revision: https://phabricator.services.mozilla.com/D65502
--HG--
extra : moz-landing-system : lando
For now only record for password manager autocomplete but the event structure is setup to support others.
Differential Revision: https://phabricator.services.mozilla.com/D66730
--HG--
extra : moz-landing-system : lando
The code in GetVisibleRect() uses the test scroll offset, but not the test zoom.
Using AutoApplyAsyncTestAttributes automatically uses both.
Differential Revision: https://phabricator.services.mozilla.com/D66956
--HG--
extra : moz-landing-system : lando
CLOSED TREE
Backed out changeset b0ef46ae3853 (bug 1611914)
Backed out changeset f93685e544c5 (bug 1605494)
--HG--
extra : amend_source : 0e196a48b4b196268ddae92af2fa00067bb6dc0b