Some configurations of SpiderMonkey wind up producing C++ switch statements of
the form
switch (..) {
default: break;
}
We hoped that they would simply be optimised out without comment. But MSVC
warns about the lack of non-default cases, which then are escalated into
errors, causing the build to fail. This commit simply disables that warning
feature when building with MSVC.
--HG--
extra : rebase_source : 468022d30cdaf483aaa64fc7aa9dd1308fbc7335
This bug is for importation of spec tests for the WA mutable-global
extension, as proposed at https://github.com/WebAssembly/mutable-global.
In particular it imports the following tests in that repo:
test/core/globals.wast (wrapped in JS)
test/core/linking.wast (ditto)
test/js-api/jsapi.js
The resulting files linking.js and globals.js are placed in a new
subdirectory, js/src/jit-test/tests/wasm/spec/proposal_mutable_global to
make it clear that they pertain to the proposal, and so as not to alter the
existing tests.
There have also been some changes to the test harness code as required to
support the new tests, as follows:
* js/src/jit-test/lib/wasm-testharness.js: the existing logic for locating
the harness/ subdir appears to assume that all the test scripts live in
the same directory, which is no longer the case. It has been reworked
so as to use a fixed offset relative to |libdir| rather than a fixed
offset from |scriptdir|.
* js/src/jit-test/lib/wasm-testharness.js: the revised jsapi.js requires a
new function |assert_not_equals|, but it does not appear possible to
define it in the same way that |assert_equals| is defined. A simple
implementation of |assert_not_equals| has therefore been added.
* src/jit-test/tests/wasm/spec/harness/index.js: a couple more registry
entries were added, as required by the new globals.js and linking.js.
* js/src/jit-test/tests/wasm/spec/harness/wasm-module-builder.js: added
a |mutable| parameter to addImportedGlobal().
* js/src/jit-test/tests/wasm/spec/jsapi.js: there are many changes, but
almost all of them result simply from the resync.
* js/src/jit-test/tests/wasm/spec/proposal_mutable_global/directives.txt
* js/src/jit-test/tests/wasm/spec/proposal_mutable_global/globals.wast.js
* js/src/jit-test/tests/wasm/spec/proposal_mutable_global/linking.wast.js
New files.
--HG--
extra : rebase_source : 1f049fced054e2a979c1ab364f75aaf805de1255
This is slightly ugly, but is unfortunately necessary due to do the nature of
l10n repacks. Hopefully this can go away once we move to bundling lancpack
add-ons rather than repacking in the future.
MozReview-Commit-ID: JZUblVsEbZI
--HG--
extra : rebase_source : 60c9ced2184a52f52c7f2a8820021b14b1a66abf
In order to have useful Wayland builds we need ability to switch
between GL backends run-time - to use EGL backend for Wayland and GLX backend for X11.
GL_PROVIDER_GLX is used exclusively for GLX GL backend, so let's replace GL_PROVIDER_GLX
build-time check by more general MOZ_X11 check which determines X11 dependent code
and it's valid for both X11 and Wayland builds.
MozReview-Commit-ID: HYobrHveoaP
--HG--
extra : rebase_source : 2d359355ee747f5898d27d8a28d66114f4135f5b
This patch prevents baseline coverage tests from being skipped when too many tests are being run.
MozReview-Commit-ID: JVTOYZAXbwf
--HG--
extra : rebase_source : dedd6a323445f030b60180805c6c6adf5d10771b
This adds section size metrics in order to track finer grained improvements
and regressions in binary size. Currently it implements tracking of:
- XUL
- NSS
- NSPR
- mozavcodec
- mozavutil
The sections tracked are limited in order to avoid too much noise:
- .text
- .data
- .rodata
- .data.rel.ro
- .bss
Currently this is limited to measure Linux and Android builds, but can be
easily extended to support other platforms once we have a `size`-like tool
available.
--HG--
extra : rebase_source : 494922e60c1ea47392e3121425d7aacef6c3003a
This adds a helper so that we consistently detect install type based on
extension the same way.
In the process, it also simplifies some of the code that tries to detect
modification times for unpacked directories, so that it only checks the
directory mtime. We don't support signatures for unpacked directories anymore,
so this has no purpose outside of developer builds with signing disabled.
Those developers can move to touching the install directory's mtime rather than
the manifest file's.
MozReview-Commit-ID: J5LwaXXqyZL
--HG--
extra : rebase_source : f2fb86159c06bbeba2500e04dcde1c565cd39c12
