зеркало из https://github.com/mozilla/gecko-dev.git
ba28962c5e
This changes the semantics of bootstrapping substantially, but all for the simpler. - --disable-bootstrap now prevents bootstrapped toolchains from being used entirely, even if they are present. - --enable-bootstrap still automatically downloads missing or out-of-date toolchains, and is still only the default when building off a VCS checkout of mozilla-central. - When neither option is given on another tree than a VCS checkout of mozilla-central, already bootstrapped toolchains are prioritized, but missing toolchains are not downloaded, and outdated toolchains are not updated. - --enable-bootstrap=no-update can now be used to replace the previous behavior of --disable-bootstrap, to avoid the automatic update of already bootstrapped toolchains, with the difference that missing toolchains are still automatically bootstrapped. This has the downside of making the semantics of the per-toolchain opt-in/opt-out mechanics introduced in bug 1828027 kind of confusing, but I'm keeping reworking that, or entirely removing it for a followup. Differential Revision: https://phabricator.services.mozilla.com/D188315 |
||
---|---|---|
.. | ||
README | ||
filter-log.pl | ||
find-comptr-leakers.pl | ||
find_leakers.py | ||
fix_stacks.py | ||
make-tree.pl |
README
This is the Refcount Balancer. See https://firefox-source-docs.mozilla.org/performance/memory/refcount_tracing_and_balancing.html for documentation. Note that the `fix_stacks.py` script is used in several other places in the repository.