about summary refs log tree commit diff
path: root/src/libstd/sys
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2018-07-11 12:12:13 +0000
committerbors <bors@rust-lang.org>2018-07-11 12:12:13 +0000
commit11432ba98043ee0ade961bdedb4b785bf06c086e (patch)
treefa90a01c30de78430012adcf37f54c2d55ea5462 /src/libstd/sys
parent989fa053895a27fd40896335224b619843b7e58a (diff)
parent3f18a41333aabf515d6d343c07f3bbbd154f6018 (diff)
downloadrust-11432ba98043ee0ade961bdedb4b785bf06c086e.tar.gz
rust-11432ba98043ee0ade961bdedb4b785bf06c086e.zip
Auto merge of #51230 - nikic:no-verify-lto, r=pnkfelix
Disable LLVM verification by default

Currently -Z no-verify only controls IR verification prior to LLVM codegen, while verification is performed unconditionally both before and after linking with (Thin)LTO.

Also wondering what the sentiment is on disabling verification by default (and e.g. only enabling it on ALT builds with assertions). This does not seem terribly useful outside of rustc development and it does seem to show up in profiles (at something like 3%).

**EDIT:** A table showing the various configurations and what is enabled when.

| Configuration | Dynamic verification performed | LLVM static assertions compiled in |
| --- | --- | --- |
| alt builds | | yes |
| nightly builds | | no |
| stable builds | | no |
| CI builds | | |
| dev builds in a checkout | | |
Diffstat (limited to 'src/libstd/sys')
0 files changed, 0 insertions, 0 deletions