-
Notifications
You must be signed in to change notification settings - Fork 12.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rollup of 11 pull requests #79167
Rollup of 11 pull requests #79167
Commits on Oct 25, 2020
-
Updated the list of white-listed target features for x86
This PR both adds in-source documentation on what to look out for when adding a new (X86) feature set and adds all that are detectable at run-time in Rust stable as of 1.27.0. This should only enable the use of the corresponding LLVM intrinsics. Actual intrinsics need to be added separately in rust-lang/stdarch. It also re-orders the run-time-detect test statements to be more consistent with the actual list of intrinsics whitelisted and removes underscores not present in the actual names (which might be mistaken as being part of the name)
Configuration menu - View commit details
-
Copy full SHA for 9feb567 - Browse repository at this point
Copy the full SHA 9feb567View commit details -
Removed movbe from run-time-detect
`movbe` seems to not be a run-time detectable feature on x86. It has thus been removed from the list. It was only commented out to ease comparison against the full list.
Configuration menu - View commit details
-
Copy full SHA for cd95e93 - Browse repository at this point
Copy the full SHA cd95e93View commit details
Commits on Oct 26, 2020
-
Updated documentation, x86 feature detection testing, and removed LLV…
…M 9 exclusive features Updated the added documentation in llvm_util.rs to note which copies of LLVM need to be inspected. Removed avx512bf16 and avx512vp2intersect because they are unsupported before LLVM 9 with the build with external LLVM 8 being supported Re-introduced detection testing previously removed for un-requestable features tsc and mmx
Configuration menu - View commit details
-
Copy full SHA for 3daa93f - Browse repository at this point
Copy the full SHA 3daa93fView commit details
Commits on Nov 12, 2020
-
Configuration menu - View commit details
-
Copy full SHA for 909c894 - Browse repository at this point
Copy the full SHA 909c894View commit details
Commits on Nov 14, 2020
-
Configuration menu - View commit details
-
Copy full SHA for 55d7f73 - Browse repository at this point
Copy the full SHA 55d7f73View commit details
Commits on Nov 15, 2020
-
Re-enable LLVM 9 target features with LLVM 9 being the minimum now
With rust-lang#78848 merged, the minimum supported LLVM version is now 9 which means we can actually use the target features introduced in LLVM 9
Configuration menu - View commit details
-
Copy full SHA for 72b83af - Browse repository at this point
Copy the full SHA 72b83afView commit details -
Configuration menu - View commit details
-
Copy full SHA for c82a258 - Browse repository at this point
Copy the full SHA c82a258View commit details
Commits on Nov 16, 2020
-
Configuration menu - View commit details
-
Copy full SHA for dcc194c - Browse repository at this point
Copy the full SHA dcc194cView commit details -
linux: try to use libc getrandom to allow interposition
We'll try to use a weak `getrandom` symbol first, because that allows things like `LD_PRELOAD` interposition. For example, perf measurements might want to disable randomness to get reproducible results. If the weak symbol is not found, we fall back to a raw `SYS_getrandom` call.
Configuration menu - View commit details
-
Copy full SHA for 7a15f02 - Browse repository at this point
Copy the full SHA 7a15f02View commit details -
Configuration menu - View commit details
-
Copy full SHA for a035626 - Browse repository at this point
Copy the full SHA a035626View commit details -
Configuration menu - View commit details
-
Copy full SHA for cd22381 - Browse repository at this point
Copy the full SHA cd22381View commit details
Commits on Nov 17, 2020
-
Configuration menu - View commit details
-
Copy full SHA for d701bf9 - Browse repository at this point
Copy the full SHA d701bf9View commit details -
bootstrap: use the same version number for rustc and cargo
Historically the stable tarballs were named after the version number of the specific tool, instead of the version number of Rust. For example, both of the following tarballs were part of the same release: rustc-1.48.0-x86_64-unknown-linux-gnu.tar.xz cargo-0.49.0-x86_64-unknown-linux-gnu.tar.xz PR rust-lang#77336 changed the dist code to instead use Rust's version number for all the tarballs, regardless of the tool they contain: rustc-1.48.0-x86_64-unknown-linux-gnu.tar.xz cargo-1.48.0-x86_64-unknown-linux-gnu.tar.xz Because of that there is no need anymore to have a separate `cargo` field in src/stage0.txt, as the Cargo version will always be the same as the rustc version. This PR removes the field, simplifying the code and the maintenance work required while producing releases.
Configuration menu - View commit details
-
Copy full SHA for d17874f - Browse repository at this point
Copy the full SHA d17874fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 9bbc4c1 - Browse repository at this point
Copy the full SHA 9bbc4c1View commit details -
This should make Clippy more resilient and will unblock rust-lang#78343. This PR is made against rust-lang/rust to avoid the need for a subtree sync at @flip1995's suggestion in rust-lang/rust-clippy#6310.
Configuration menu - View commit details
-
Copy full SHA for 95eff66 - Browse repository at this point
Copy the full SHA 95eff66View commit details -
Fix typo in
std::io::Write
docsThese referred to a “`Write`er”—extra *e*. Presumably a copy-paste holdover from “`Read`er”. Test Plan: Running ``git grep '`\?[Ww]rite`\?er'`` no longer finds any results. wchargin-branch: io-write-docs
Configuration menu - View commit details
-
Copy full SHA for bdaa76c - Browse repository at this point
Copy the full SHA bdaa76cView commit details
Commits on Nov 18, 2020
-
Configuration menu - View commit details
-
Copy full SHA for 88584d5 - Browse repository at this point
Copy the full SHA 88584d5View commit details -
Rollup merge of rust-lang#78361 - DevJPM:master, r=workingjubilee
Updated the list of white-listed target features for x86 This PR both adds in-source documentation on what to look out for when adding a new (X86) feature set and [adds all that are detectable at run-time in Rust stable as of 1.27.0](https://github.com/rust-lang/stdarch/blob/master/crates/std_detect/src/detect/arch/x86.rs). This should only enable the use of the corresponding LLVM intrinsics. Actual intrinsics need to be added separately in rust-lang/stdarch. It also re-orders the run-time-detect test statements to be more consistent with the actual list of intrinsics whitelisted and removes underscores not present in the actual names (which might be mistaken as being part of the name) The reference for LLVM's feature names used is [this file](https://github.com/llvm/llvm-project/blob/master/llvm/include/llvm/Support/X86TargetParser.def). This PR was motivated as the compiler end's part for allowing rust-lang#67329 to be adressed over on rust-lang/stdarch
Configuration menu - View commit details
-
Copy full SHA for c7e9029 - Browse repository at this point
Copy the full SHA c7e9029View commit details -
Rollup merge of rust-lang#78785 - cuviper:weak-getrandom, r=m-ou-se
linux: try to use libc getrandom to allow interposition We'll try to use a weak `getrandom` symbol first, because that allows things like `LD_PRELOAD` interposition. For example, perf measurements might want to disable randomness to get reproducible results. If the weak symbol is not found, we fall back to a raw `SYS_getrandom` call.
Configuration menu - View commit details
-
Copy full SHA for 61134aa - Browse repository at this point
Copy the full SHA 61134aaView commit details -
Rollup merge of rust-lang#78999 - petrochenkov:deprid, r=eddyb
stability: More precise location for deprecation lint on macros One missing piece of rust-lang#73178.
Configuration menu - View commit details
-
Copy full SHA for 92dcf6d - Browse repository at this point
Copy the full SHA 92dcf6dView commit details -
Rollup merge of rust-lang#79039 - thomcc:weakly-relaxing, r=Amanieu
Tighten the bounds on atomic Ordering in std::sys::unix::weak::Weak This moves reading this from multiple SeqCst reads to Relaxed read + Acquire fence if we are actually going to use the data. Would love to avoid the Acquire fence, but doing so would need Ordering::Consume, which neither Rust, nor LLVM supports (a shame, since this fence is hardly free on ARM, which is what I was hoping to improve). r? ``@Amanieu`` (Sorry for always picking you, but I know a lot of people wouldn't feel comfortable reviewing atomic ordering changes)
Configuration menu - View commit details
-
Copy full SHA for ad6fd9b - Browse repository at this point
Copy the full SHA ad6fd9bView commit details -
Rollup merge of rust-lang#79079 - camelid:mir-visit-docs, r=matthewja…
…sper Turn top-level comments into module docs in MIR visitor
Configuration menu - View commit details
-
Copy full SHA for f85c3f7 - Browse repository at this point
Copy the full SHA f85c3f7View commit details -
Rollup merge of rust-lang#79114 - andjo403:nonzero_leading_trailing_z…
…eros, r=m-ou-se add trailing_zeros and leading_zeros to non zero types as a way towards being able to use the optimized intrinsics ctlz_nonzero and cttz_nonzero from stable. have not crated any tracking issue if this is not a solution that is wanted
Configuration menu - View commit details
-
Copy full SHA for 126d88b - Browse repository at this point
Copy the full SHA 126d88bView commit details -
Rollup merge of rust-lang#79131 - vertexclique:stdarch-update, r=Amanieu
Enable AVX512 *epi64 variants by updating stdarch
Configuration menu - View commit details
-
Copy full SHA for e2addb4 - Browse repository at this point
Copy the full SHA e2addb4View commit details -
Rollup merge of rust-lang#79133 - pietroalbini:simplify-stage0, r=Mar…
…k-Simulacrum bootstrap: use the same version number for rustc and cargo Historically the stable tarballs were named after the version number ofthe specific tool, instead of the version number of Rust. For example, both of the following tarballs were part of the same release: rustc-1.48.0-x86_64-unknown-linux-gnu.tar.xz cargo-0.49.0-x86_64-unknown-linux-gnu.tar.xz PR rust-lang#77336 changed the dist code to instead use Rust's version number for all the tarballs, regardless of the tool they contain: rustc-1.48.0-x86_64-unknown-linux-gnu.tar.xz cargo-1.48.0-x86_64-unknown-linux-gnu.tar.xz Because of that there is no need anymore to have a separate `cargo` field in `src/stage0.txt`, as the Cargo version will always be the same as the rustc version. This PR removes the field, simplifying the code and the maintenance work required while producing releases. r? ``@Mark-Simulacrum``
Configuration menu - View commit details
-
Copy full SHA for 83fcbd5 - Browse repository at this point
Copy the full SHA 83fcbd5View commit details -
Rollup merge of rust-lang#79145 - camelid:clippy-fix-panics, r=flip1995
Fix handling of panic calls This should make Clippy more resilient and will unblock rust-lang#78343. This PR is made against rust-lang/rust to avoid the need for a subtree sync at ``@flip1995's`` suggestion in rust-lang/rust-clippy#6310. r? ``@flip1995`` cc ``@m-ou-se``
Configuration menu - View commit details
-
Copy full SHA for 20fbe22 - Browse repository at this point
Copy the full SHA 20fbe22View commit details -
Rollup merge of rust-lang#79151 - wchargin:wchargin-io-write-docs, r=…
…jyn514 Fix typo in `std::io::Write` docs These referred to a “`Write`er”—extra *e*. Presumably a copy-paste holdover from “`Read`er”. Test Plan: Running ``git grep '`\?[Ww]rite`\?er'`` no longer finds any results. wchargin-branch: io-write-docs
Configuration menu - View commit details
-
Copy full SHA for 5a9104f - Browse repository at this point
Copy the full SHA 5a9104fView commit details -
Rollup merge of rust-lang#79158 - lcnr:lazy-norm-coerce, r=oli-obk
type is too big -> values of the type are too big strictly speaking, `[u8; usize::MAX]` or even `[[[u128; usize::MAX]; usize::MAX]; usize::MAX]` are absolutely fine types as long as you don't try to deal with any values of it. This error message seems to cause some confusion imo, for example in rust-lang#79135 (comment) so I would prefer us to be more precise here. See the added test case which uses one of these types without causing an error. r? ``@oli-obk``
Configuration menu - View commit details
-
Copy full SHA for 43d13e2 - Browse repository at this point
Copy the full SHA 43d13e2View commit details