diff options
| author | Takayuki Maeda <takoyaki0316@gmail.com> | 2024-01-11 15:41:46 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-01-11 15:41:46 +0900 |
| commit | ef1e49a641e00d30066c5c32e53972cf76e7838c (patch) | |
| tree | c1a07befd9b84c77b2e596dbdbe1a5cd6d02ba1f /library/std/src/sys/unix/os.rs | |
| parent | 6794dc9a5fa86be24fa4a1c1464167f3e390d916 (diff) | |
| parent | 837be0de5f50196227660abf68b47d1412596568 (diff) | |
| download | rust-ef1e49a641e00d30066c5c32e53972cf76e7838c.tar.gz rust-ef1e49a641e00d30066c5c32e53972cf76e7838c.zip | |
Rollup merge of #119814 - nagisa:nagisa/releases-the-link-jobs-demons, r=clubby789
bootstrap: exclude link_jobs from `check_ci_llvm!` checks This option is largely there to help people to manage the memory usage on their systems during the LLVM build. The linking phase is as usual are the heaviest part of the build and if in an unlucky conincidence the circumstances align to kick off N_CORES links at the same time, not even hundreds of GiB of memory may suffice. It makes a lot of sense for developers to set&forget this option unconditionally based on how buff their development device is. Not to mention, this option does not, in any way, affect the generated code (at least as far as I know.) It really doesn’t matter what option the CI build LLVM used here and/or if it matches with the user’s configuration. Finally, 0 actual link jobs implied by `download-ci-llvm` is guaranteed to stay within the limits that are reasonable to set with this option.
Diffstat (limited to 'library/std/src/sys/unix/os.rs')
0 files changed, 0 insertions, 0 deletions