This removes the menu separators frmo the developer tools menu to conform to
the proton design.
We can safely remove the "devToolsEndSeparator" separator since it is no longer
used to append the "Work Offline" that is removed in Part 4.
We change the anchor element to be the "menu_devtools_remotedebugging" menu item
with the removal oof the "menu_devtools_separator" separator.
Differential Revision: https://phabricator.services.mozilla.com/D104904
While building the object literal code, use bloom-filter to quickly detect
possible duplicate properties, and when finishing, check duplicate properties
using hash-set, if possible duplicate properties were detected.
Differential Revision: https://phabricator.services.mozilla.com/D104692
This is a test-only change.
The "UntrustedModulesFixture.Serialize" test fails on ASan build of mozilla-beta
and mozilla-release because the current value of waiting cycles 200 is not enough
to collect all expected loading events, while it's enough on the normal build or
mozilla-central.
This patch is simply to increase the number of cycles to 500. Test logs show
ASan build of mozilla-betal or mozilla-release needs about 250 cycles to collect
all expected loading events, so 500 should be enough.
Differential Revision: https://phabricator.services.mozilla.com/D105363
This doesn't use a full bitmap for every single rule type, as we only expect
that keyframe, page, and style rules will be checked.
Differential Revision: https://phabricator.services.mozilla.com/D104949
Because the previous commit changed how MFBT tests are linked, they now
use mozjemalloc. Mozjemalloc randomizes small allocations, which id does
by using MFBT's RandomNum. The code in RandomNum, on mac, uses a system
API that allocates memory. So mozjemalloc has some code to handle the
recursion gracefully.
When the RandomNum test runs, it essentially only runs the RNG... which
goes on to allocate memory, which then goes into the RNG. Needless to
say, that doesn't go well. In typical cases, this is not the type of
things that would happen, but it does happen for that one test.
We work around the issue by allocating memory first, which is actually
hard, because compilers like to optimize unused allocations away. So we
turn the existing code into one that uses an allocation instead of an
array on the stack.
Differential Revision: https://phabricator.services.mozilla.com/D105242
Instead of snprintf.
Because some standalone code uses those functions directly or indirectly,
and PrintfTarget lives in mozglue, they now need to depend on mozglue
instead of mfbt. Except logalloc/replay, which cherry-picks what it
uses.
Differential Revision: https://phabricator.services.mozilla.com/D103730
For YUV 422 video, when we are sampling UV planes at half the resolution of the
Y plane, we can interpolate from 2 samples for the UV planes as an approximation
of the 4 samples, allowing us to better pack the math into SIMD vectors and
substantially reduce the number of multiplications.
Differential Revision: https://phabricator.services.mozilla.com/D105137
Often images are upscaled from a smaller resolution on a page, especially
when there is any amount of zoom being used, and especially at higher screen
resolutions. In this case, we don't really take advantage of the fact that all
the samples for a SIMD chunk can be loaded from memory in a single load, so
long as we're willing to shuffle them around. We also can take advantage of the
fact that most images are axis-aligned so that they have a constant filter
offset with the next row.
Also, we can easily fall off the fast past for blendTextureNearest if for some
reason there is a significant subpixel offset. In this case, we can still do
something way faster than a normal linear filter the optimizes for the fact
that both the X and Y steps are constant 1:1, but we need to interpolate with
neighboring samples.
Differential Revision: https://phabricator.services.mozilla.com/D105131
None of HAVE_NASM, HAVE_YASM, NASM_MAJOR_VERSION and NASM_MINOR_VERSION are
used. Also, the YASM variable is not necessary for old-configure anymore.
Differential Revision: https://phabricator.services.mozilla.com/D105269
Building the ICU data file hasn't required yasm since bug 1650299, and
all the compilers we support now have a GAS-like assembler that we use
unconditionally.
Differential Revision: https://phabricator.services.mozilla.com/D105268