We cannot be sure about unknown (that's what we might get on some tier-3
platforms), but if we get e.g. "ld64" while building for Linux, that's
clearly wrong.
Differential Revision: https://phabricator.services.mozilla.com/D134909
AC_CHECK_FUNC doesn't automatically set HAVE_$function defines
(AC_CHECK_FUNCS does, confusing much?). Which means practically
speaking, the check is not useful. There _are_ #ifdef HAVE_FDATASYNC
in sqlite, but fdatasync is notably broken on older kernels, and while
lmdb has runtime workarounds for that, sqlite doesn't. It might be fine
to enable the sqlite code because those kernels are old, but this is
not a straightforward decision to make at the build system level, so
we'll handle that in a followup.
Differential Revision: https://phabricator.services.mozilla.com/D134855
HAVE_LCHOWN is only used in nsinstall.c, for a feature we don't use.
Moreover it would need to be tested with the host compiler/headers, but
function checks are tested with the target compiler/headers so it's not
necessarily accurate. Therefore, we just remove the check.
Differential Revision: https://phabricator.services.mozilla.com/D134854
Use the SHT_RELR format which significantly improves the size reduction
from elfhack:
total size of .rel.* + .elfhack.* sections
x86 x86_64 android-arm
plain 3532904 10739544 3488888
current-elfhack 1085815 1155994 1042048
relr-elfhack 130219 193552 113840
Differential Revision: https://phabricator.services.mozilla.com/D134756
Also:
* Add label for WebGLContext::Create.
* *Remove* label for WebGLContext::Draw*, since the labels for these are
showing up in draw-call-heavy profiles. (~1.5%)
* WebGLContext::UniformData continues to not have a label, since that
would likely add another 2-3% labelling overhead.
* Add missing !mHost check to RecvTexImage.
Differential Revision: https://phabricator.services.mozilla.com/D134883
With bug 1743926 apparently done, bug 1744777 so far appears to be the only
reason not to ship to release. Given that bug 1744777 likely also applies
to VP9, that's probably acceptable. On the pro-side are better sandboxing
and easy to enable VAAPI decoding.
So let's ship.
Differential Revision: https://phabricator.services.mozilla.com/D134890
While mingw builds don't require user32 and advapi32 explicitly, it doesn't
hurt for them to be there (and they're required for clang-cl build).
Likewise, while clang-builds don't require uuid and userenv explicitly
because they're pulled in via #pragmas in the source code, mingw doesn't
support those #pragmas and needs them explicitly, which doesn't hurt the
clang-cl builds.
Differential Revision: https://phabricator.services.mozilla.com/D134737
This commit did a fresh pull of all our vendored
spec-test repositories. I updated all repositories instead
of just the exception-handling one so that diffs between
base and dependent proposals remained minimized.
Differential Revision: https://phabricator.services.mozilla.com/D134631
This commit changes the throw stub to clobber most registers
before jumping to the catch landing pad. The exact details of
which registers to clobber is commented in the stub.
Differential Revision: https://phabricator.services.mozilla.com/D134630
This allows generating libwebrtc build files for OpenBSD and does
_not_ change the current build output on the other supported
platforms.
Differential Revision: https://phabricator.services.mozilla.com/D134881
* Don't include partially matching engines that are already in the perfectly
matching list
* Add a test for this and the `matchAllDomainLevels` case in general since we
don't have one AFAICT
* The test file name ends in jsm, so change it to js
Differential Revision: https://phabricator.services.mozilla.com/D134811
The CSS-text-decoration spec doesn't explicitly say anything about maintaining the dotted-line pattern
continuously across direction-run or inline-element boundaries, which is what this is testing,
but I think that follows from the fact that in each example here, there is a single "decorating box"
involved (and not separate, independently-decorated boxes for each direction-run or span).
Differential Revision: https://phabricator.services.mozilla.com/D134870
The CSS-text-decoration spec doesn't explicitly say anything about maintaining the dotted-line pattern
continuously across direction-run or inline-element boundaries, which is what this is testing,
but I think that follows from the fact that in each example here, there is a single "decorating box"
involved (and not separate, independently-decorated boxes for each direction-run or span).
Depends on D134783
Differential Revision: https://phabricator.services.mozilla.com/D134870
It is an edge case that InterceptedHttpChannel::Cancel() could be called before calling AsyncOpenInternal().
In the case, mTimeStamp status would be Created and we should not record any time stamp for InterceptedHttpChannel.
Differential Revision: https://phabricator.services.mozilla.com/D134775
