Back when libaom was added, VPX_ASFLAGS was more or less the only
variable that had the right set of flags for NEON support, which
justified its use. However, it's not set when building against system
libvpx.
Bug 1791482 improved things, though, and VPX_ASFLAGS, as far as NEON is
concerned, is now only re-exporting NEON_FLAGS, with the same caveat that
VPX_ASFLAGS is empty when building against system libvpx.
So we should use NEON_FLAGS instead of VPX_ASFLAGS.
Differential Revision: https://phabricator.services.mozilla.com/D183310
Renames patches to force ordering.
simd-detect-runtime.patch was not applying cleanly, so slightly update
its context. No impact on the final source.
Differential Revision: https://phabricator.services.mozilla.com/D182993
This makes the types from mozbuild.configure.constants repr()-able, and
repr()-ed in config.status, which, when processing moz.build, translates
into value checking for comparison tests involving the variables.
To make them pickable, though, we replace the use of EnumString.subclass
with actual subclassing, which is a little less convenient, but avoids
having to figure out how to make the classes EnumString.subclass creates
pickable.
This caught some mismatches in media/libpng and third_party/libsrtp.
This also means we don't need to normalize the config before dumping it
in config.status, because the only types that this was actually useful
for are these (historically, we'd also turn byte strings into unicode
strings but that hasn't been a thing for 4 years ; the special treatment
of dicts and iterables was there to apply the normalization recursively,
not to normalize dicts and iterables themselves). We still normalization
before passing values to gyp, though.
Differential Revision: https://phabricator.services.mozilla.com/D182141
This makes the types from mozbuild.configure.constants repr()-able, and
repr()-ed in config.status, which, when processing moz.build, translates
into value checking for comparison tests involving the variables.
To make them pickable, though, we replace the use of EnumString.subclass
with actual subclassing, which is a little less convenient, but avoids
having to figure out how to make the classes EnumString.subclass creates
pickable.
This caught a mismatch in media/libpng.
Differential Revision: https://phabricator.services.mozilla.com/D182141
This makes the types from mozbuild.configure.constants repr()-able, and
repr()-ed in config.status, which, when processing moz.build, translates
into value checking for comparison tests involving the variables.
This caught a mismatch in media/libpng.
Differential Revision: https://phabricator.services.mozilla.com/D182141
The same main thread task that may expose RTCRtpTransceiver (and its receiver
and sender) connects the conduit mirrors through an async task on the call
thread. If js does something that triggers a regular task to be dispatched to
the call thread, that task cannot make assumptions on the state of the conduit.
With this patch enabling canonical-initialization, conduit and pipeline mirrors
are connected synchronously, and a task like that mentioned above is guaranteed
to arrive after the first canonical statechange task, meaning it *can* make
assumptions on the state of the class owning the mirrors.
Differential Revision: https://phabricator.services.mozilla.com/D180429
The same main thread task that may expose RTCRtpTransceiver (and its receiver
and sender) connects the conduit mirrors through an async task on the call
thread. If js does something that triggers a regular task to be dispatched to
the call thread, that task cannot make assumptions on the state of the conduit.
With this patch enabling canonical-initialization, conduit and pipeline mirrors
are connected synchronously, and a task like that mentioned above is guaranteed
to arrive after the first canonical statechange task, meaning it *can* make
assumptions on the state of the class owning the mirrors.
Differential Revision: https://phabricator.services.mozilla.com/D180429
Upstream highway project has a check for the availability of the asm/hwcap.h
header, because it doesn't exist on all platforms. Work around it statically
in moz.build.
Differential Revision: https://phabricator.services.mozilla.com/D181468
With the requirement that `cargo vet` goes through, testing things out
can be annoying. Add a --force option that allows to temporarily ignore
problems. This also replaces the --build-peers-said-large-imports-were-ok
flag.
Differential Revision: https://phabricator.services.mozilla.com/D179512