zlib still uses K&R-style function declarations. As of clang 15, these
are warned about by default, as they've been removed in the latest draft
of C2x; this results in thousands(?) of lines of warnings when building
zlib in-tree.

An issue has been filed at https://github.com/madler/zlib/issues/633,
but the author has stated that they are unwilling to change this until
C2x has actually been published.

For now, just silence those warnings when building zlib.

Differential Revision: https://phabricator.services.mozilla.com/D169842

Differential Revision: https://phabricator.services.mozilla.com/D159950

Differential Revision: https://phabricator.services.mozilla.com/D142350

Differential Revision: https://phabricator.services.mozilla.com/D144142

This bug was reported by Danilo Ramos of Eideticom, Inc. It has
lain in wait 13 years before being found! The bug was introduced
in zlib 1.2.2.2, with the addition of the Z_FIXED option. That
option forces the use of fixed Huffman codes. For rare inputs with
a large number of distant matches, the pending buffer into which
the compressed data is written can overwrite the distance symbol
table which it overlays. That results in corrupted output due to
invalid distances, and can result in out-of-bound accesses,
crashing the application.

The fix here combines the distance buffer and literal/length
buffers into a single symbol buffer. Now three bytes of pending
buffer space are opened up for each literal or length/distance
pair consumed, instead of the previous two bytes. This assures
that the pending buffer cannot overwrite the symbol table, since
the maximum fixed code compressed length/distance is 31 bits, and
since there are four bytes of pending space for every three bytes
of symbol space.

Differential Revision: https://phabricator.services.mozilla.com/D142231

This bug was reported by Danilo Ramos of Eideticom, Inc. It has
lain in wait 13 years before being found! The bug was introduced
in zlib 1.2.2.2, with the addition of the Z_FIXED option. That
option forces the use of fixed Huffman codes. For rare inputs with
a large number of distant matches, the pending buffer into which
the compressed data is written can overwrite the distance symbol
table which it overlays. That results in corrupted output due to
invalid distances, and can result in out-of-bound accesses,
crashing the application.

The fix here combines the distance buffer and literal/length
buffers into a single symbol buffer. Now three bytes of pending
buffer space are opened up for each literal or length/distance
pair consumed, instead of the previous two bytes. This assures
that the pending buffer cannot overwrite the symbol table, since
the maximum fixed code compressed length/distance is 31 bits, and
since there are four bytes of pending space for every three bytes
of symbol space.

Differential Revision: https://phabricator.services.mozilla.com/D142231

To compile SM to .wasm we need to use clang from wasi-sdk, this patch
allows us to use default clang-12 from mozilla's repo.
We remove usage of rpath-link flag because wasm-ld doesn't support it,
enable single thread model because wasi is single threaded
and finally add <unistd.h> becase it is forbidden to use read/write/lseek
without this header.

Differential Revision: https://phabricator.services.mozilla.com/D116207

Bug 1679938 - Don't recurse the build into mfbt for projects that don't need it. r=firefox-build-system-reviewers,mhentges

While all toolkit and js-based projects make use of mfbt, some others,
like tools/crashreporter and tools/update-packaging, don't.

So instead of including mfbt from the top-level directory, include it
from the relevant project top-level mozbuilds.

This allows to remove the dependency on mfbt files in the hash for the
minidump-stackwalk and mar-tools toolchains.

Differential Revision: https://phabricator.services.mozilla.com/D98378

It was remaining from an earlier iteration of bug 1418425 that uses
zlib's crc32 function, but ended up unused because in the end it was
done differently.

Interestingly, the corresponding host objects are not built currently,
and actually fail to build when built manually (or with build system
changes that make them built).

Differential Revision: https://phabricator.services.mozilla.com/D42073

--HG--
extra : moz-landing-system : lando

The current situation is suboptimal, where we have the same goop
repeated in multiple files, and where things kinda sorta work out fine
thanks to the linker for files that would have been forbidden, except
when the linker doesn't do its job, which apparently happen on
mingwclang builds.

This change only really covers C++ code using operator new/delete, and
not things that would be using malloc/free, because it's easier.
malloc/free is left for a followup.

Differential Revision: https://phabricator.services.mozilla.com/D32119

--HG--
extra : moz-landing-system : lando

Backed out changeset 0ecc98bd0822 (bug 1418425)
Backed out changeset 7b7725d1d3c3 (bug 1418425)
Backed out changeset 2e95ebdcae6d (bug 1418425)
Backed out changeset 47fbcaf5ad05 (bug 1418425)
Backed out changeset 142001babb39 (bug 1418425)

--HG--
extra : source : 492a154a477f9f38122a5214367a95b76c82b560

Backed out changeset 0ecc98bd0822 (bug 1418425)
Backed out changeset 7b7725d1d3c3 (bug 1418425)
Backed out changeset 2e95ebdcae6d (bug 1418425)
Backed out changeset 47fbcaf5ad05 (bug 1418425)
Backed out changeset 142001babb39 (bug 1418425)

MozReview-Commit-ID: 5jXyVhRI0kD

--HG--
extra : rebase_source : 0d189eb31853f4eb693cc6ffb3188f9104881274

Backed out 5 changesets (bug 1418425) for windows build bustage "mbsdiff.exe : fatal error LNK1120". on a CLOSED TREE

Backed out changeset 8154486d3e00 (bug 1418425)
Backed out changeset d32ae48690a7 (bug 1418425)
Backed out changeset 772538a846cb (bug 1418425)
Backed out changeset 29fd023f999f (bug 1418425)
Backed out changeset 218077e82115 (bug 1418425)

MozReview-Commit-ID: 5jXyVhRI0kD

--HG--
extra : rebase_source : 0260fe4e64e6a9047c915ef1a6e77c7f92d81e24

Backed out 5 changesets (bug 1418425) for Windows updater bustages and xpshell failures on toolkit/mozapps/update/tests/unit_base_updater/marSuccessPartial.js r=backout on a CLOSED TREE

Backed out changeset 228743018ded (bug 1418425)
Backed out changeset f29f7bb3059a (bug 1418425)
Backed out changeset 1d798e14223b (bug 1418425)
Backed out changeset fd4af65bf966 (bug 1418425)
Backed out changeset 656649ecfb11 (bug 1418425)

--HG--
extra : amend_source : 686bbebdb6f490496f9c69ccff4ac22bbb495ad5

MozReview-Commit-ID: 5jXyVhRI0kD

--HG--
extra : rebase_source : 5c80f5210f895cc935937e380c6f406b8fb61f1f

MozReview-Commit-ID: G3hG5C4P5jS

This removes the unnecessary setting of c-basic-offset from all
python-mode files.

This was automatically generated using

    perl -pi -e 's/; *c-basic-offset: *[0-9]+//'

... on the affected files.

The bulk of these files are moz.build files but there a few others as
well.

MozReview-Commit-ID: 2pPf3DEiZqx

--HG--
extra : rebase_source : 0a7dcac80b924174a2c429b093791148ea6ac204

This is the following commit from upstream: e54e1299404101a5a9d0cf5e45512b543967f958

MozReview-Commit-ID: 5jXyVhRI0kD

--HG--
extra : rebase_source : eb4df10567fa341b3611b568a397b01210f449aa

* * *
Bug 1047267 - To fold with "Move remaining OS_LIBS and EXTRA_LIBS to moz.build"

Backout changeset 3fd4b546eed4 (bug 874266) and changeset a35d2e3a872f (bug 942043) for ASAN build bustage and Windows test bustage

--HG--
extra : amend_source : f20d09aeff1c8b5cbd0f1d24c7ce04e86f3aed1d

--HG--
extra : rebase_source : 385d3fd65475ffc18ee44ae088753649470e214b

--HG--
extra : rebase_source : 8de9c7f68a953e574dda22f8c14c2b2ca60444f9

--HG--
extra : rebase_source : 004a756492323e1a049586e85b3be5037159df20