Also reenable the `static_assert` which was disabled for some reason in
bug 1308236. (Bug 1308236 doesn't contain any information why this assertion
had to be disabled.)
Differential Revision: https://phabricator.services.mozilla.com/D67662
--HG--
extra : moz-landing-system : lando
This removes tracing for the values of the registration map and the active record set and sweeps them instead. This requires maintaining a map of FinalizationRegistryObjects on the zone.
Differential Revision: https://phabricator.services.mozilla.com/D67677
--HG--
extra : moz-landing-system : lando
This commit updates the config/scripts for the latest wasm-generate-testsuite.
* Remove wasm-spec-tests.patch as it's not actually being used due to typo
* Switch to explicit lockfile that is updated separately
* Exclude tests that are failing when correctly imported for the current
pinned commits.
- This was due to an incorrectly implemented find files function that would
stop finding files after the first encountered directory.
Differential Revision: https://phabricator.services.mozilla.com/D67565
--HG--
extra : moz-landing-system : lando
Whenever Ion multiplies two integers on ARM64, if the result is zero, we will not only bail out, but invalidate the script. This is causing repeated invalidations in Servo. This patch fixes the negative zero handling for LMulI on ARM64.
Differential Revision: https://phabricator.services.mozilla.com/D67485
--HG--
extra : moz-landing-system : lando
This patch adds the boilerplate necessary to support a new regexp flag. Externally visible changes (parsing the flag, the dotAll property on the prototype) are guarded behind ENABLE_NEW_REGEXP.
The actual implementation of dotAll comes for free with the fresh import of irregexp (bug 1367105).
There is one test (tests/non262/RegExp/prototype.js) that needs to be updated when this is turned on to add "dotAll" to the list of expected properties on the RegExp prototype. I will attach that change to my patch that flips ENABLE_NEW_REGEXP to be on by default.
Differential Revision: https://phabricator.services.mozilla.com/D66844
--HG--
extra : moz-landing-system : lando
This adds a JS shell command line argument to disable multi-value (if
it is enabled at compile time) and an about:config option to do the
same in the browser.
At this time, multi-values are not enabled in the browser, so the
about:config option is not visible.
Differential Revision: https://phabricator.services.mozilla.com/D67465
--HG--
extra : moz-landing-system : lando
For JSOp::Object we call setSingletonsAsValues in WarpOracle. There's a comment
for CompileRealm::setSingletonsAsValues claiming it's safe to do that off-thread
but it's simpler and safer to just avoid it.
Differential Revision: https://phabricator.services.mozilla.com/D67452
--HG--
extra : moz-landing-system : lando
The change in GetIntrinsicValue is necessary. IonBuilder adds a resume point
after MCallGetIntrinsicValue but in WarpBuilder that doesn't work: because the
instruction is not effectful, it would trigger an assertion failure in resumeAfter.
Without its own resume point, however, we can't look up the current pc in
GetIntrinsicValue (the pc comes from the last resume point) so disable that code
if WarpBuilder is enabled.
Differential Revision: https://phabricator.services.mozilla.com/D67346
--HG--
extra : moz-landing-system : lando
An earlier change would disable SharedArrayBuffer in the JS shell for beta and release builds.
This has uncovered some broken guards in various test cases, in this case, a test on whether
the shell built-in setSharedObject is available. However, that is not affected by the change
in the setting, so the guard really should test both setSharedObject (to ensure it's only
tested in the shell) and SharedArrayBuffer (to ensure it's only tested when shared memory
is available.)
Differential Revision: https://phabricator.services.mozilla.com/D67474
--HG--
extra : moz-landing-system : lando
I made some changes in preparation for removing nsIScriptError.flags in favor
of nsIConsoleMessage.logLevel.
Differential Revision: https://phabricator.services.mozilla.com/D66878
--HG--
extra : moz-landing-system : lando
There are a few comments which talk about how this flag is used for
error propagation. As far as I can tell we don't actually do this.
I suspect we haven't been doing it since we have proper DOM bindings,
but I haven't actually investiaged it further.
Differential Revision: https://phabricator.services.mozilla.com/D66877
--HG--
extra : moz-landing-system : lando
yulia
Zhao Jiazhong
Tom Schuster
André Bargull
grtsid
Jeff Walden
Jon Coppeard
Matthew Gaudet
Ryan Hunt
Iain Ireland
Mihai Alexandru Michis
Steve Fink
Lars T Hansen
Jan de Mooij
caroline
Oana Pop Rus