* the certificates were regenerated using `./mach generate-test-certs`
* the build/pgo/certs/ changes were made using
`./mach python build/pgo/genpgocert.py`
* the zip files in security/manager/ssl/tests/unit/test_signed_apps/ were
updated per the directions in the corresponding moz.build file
* security/manager/ssl/tests/unit/test_cert_override_read.js needed manual
updating
These certificates and other test artifacts will now expire in 2025.
Differential Revision: https://phabricator.services.mozilla.com/D199156
* the certificates were regenerated using `./mach generate-test-certs`
* the build/pgo/certs/ changes were made using
`./mach python build/pgo/genpgocert.py`
* the zip files in security/manager/ssl/tests/unit/test_signed_apps/ were
updated per the directions in the corresponding moz.build file
* security/manager/ssl/tests/unit/test_cert_override_read.js needed manual
updating
These certificates and other test artifacts will now expire in 2025.
Test Plan:
https://treeherder.mozilla.org/jobs?repo=try&revision=04e3780551b5e83a70b51acd84e1b3383a249f14
Differential Revision: https://phabricator.services.mozilla.com/D199156
Some third party code (cairo, pixman, some media libs) rely on this
define being set. When they are built standalone, they get it from
autoconf, but we don't run their configure scripts, so that's missed.
Differential Revision: https://phabricator.services.mozilla.com/D185351
I'm pretty sure there are other theoretical problems in the code,
notably when a single section is larger than 4GB, but by the time
we reach that limit, bug 1839740 will have been fixed.
Differential Revision: https://phabricator.services.mozilla.com/D182447
There was a syntax error introduced in bug 1796380 that removed the flag
entirely. In practice, it didn't make a difference for us because clang
now defaults to PIE, but it can make a difference in environments where
the compiler is not using such a default.
However, on both Darwin and WASI, clang complains the flag is unused, so
we have to do something about it.
Differential Revision: https://phabricator.services.mozilla.com/D180279
It's only used by glean in code that is not actually used. It allows to
remove the only use of dashmap, which is a rather complex crate.
Differential Revision: https://phabricator.services.mozilla.com/D179747
Clang 17 made a change that made it an error to undefine _FORTIFY_SOURCE
on mac, because it's defined as a builtin when ASAN is enabled.
Defining it as 0 has the same effect of disabling it, but avoids the
error.
Differential Revision: https://phabricator.services.mozilla.com/D179398
We have less constraints on the minimum supported clang-cl version, and
it would unlock C++17 inline variables (which had a bug on Windows
targets in clang up-to 8.x).
Differential Revision: https://phabricator.services.mozilla.com/D179037
The situation is confusing enough.
Eventually, we'll want to have TARGET_FOO mean the same as target.foo,
but let's start with the easy one.
Differential Revision: https://phabricator.services.mozilla.com/D179178
clang 17 is making void* deref a non-disablable error, and this tests
relies on the deref "error" being disablable. Arranging things to make
it not deref makes not different from test_ref_9, so remove it.
Differential Revision: https://phabricator.services.mozilla.com/D179031
At the same time, fix the sole use of the tool to actually use what's
found by configure, and only enable that configure check when building
Spidermonkey standalone.
And while we're here, add llvm-install-name-tool to the list.
Differential Revision: https://phabricator.services.mozilla.com/D178749
Nothing in the build system is using it anymore. It is still used on some
taskcluster tasks, but those are outside the build system.
Differential Revision: https://phabricator.services.mozilla.com/D178748
The compiler may be imperfect but it evolves, and hard-coded threshold
don't. Plus according to prefherder, the impact on size is within
reasonable bounds.
Differential Revision: https://phabricator.services.mozilla.com/D178152
This doesn't change behavior, it just adds an option to disable
thread-safety analysis in local builds. I want to measure it in
different machines, and this would be useful for that. It's also useful
to workaround stuff like bug 1833676 which causes my builds to OOM
frequently.
Differential Revision: https://phabricator.services.mozilla.com/D178540
