mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-21 09:15:35 +00:00
1396262e0e
We've not been checking the clang-cl version in use. This lack of checking is bad, for a couple of reasons: * Released versions of clang-cl differ drastically in their robustness; * Only the most recent version of clang-cl supports aarch64. We should check for a minimum version of clang-cl, just like our other supported compilers. As a bonus, we can then start depending on features that we know appear in the particular minimum clang-cl version. (The current patch is motivated by `/clang:` command-line support, but one could pick other things.) Differential Revision: https://phabricator.services.mozilla.com/D30723 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| devtools/migrate-l10n | ||
| docs | ||
| l10n | ||
| mach | ||
| mozboot | ||
| mozbuild | ||
| mozlint | ||
| mozrelease | ||
| mozterm | ||
| mozversioncontrol | ||
| safety | ||
| mach_commands.py | ||
| moz.build | ||
| README | ||
This directory contains common Python code. The basic rule is that if Python code is cross-module (that's "module" in the Mozilla meaning - as in "module ownership") and is MPL-compatible, it should go here. What should not go here: * Vendored python modules (use third_party/python instead) * Python that is not MPL-compatible (see other-licenses/) * Python that has good reason to remain close to its "owning" (Mozilla) module (e.g. it is only being consumed from there). Historical information can be found at https://bugzilla.mozilla.org/show_bug.cgi?id=775243 https://bugzilla.mozilla.org/show_bug.cgi?id=1346025