rust/compiler/rustc_target at 2f6e85567af202e5fd9f4e20c194396806fe949f - bjoernager/rust

Matthias Krüger 2f6e85567a Rollup merge of #129863 - RalfJung:target-spec-features, r=wesleywiser update comment regarding TargetOptions.features The claim that `-Ctarget-features` cannot disable these features set in the target spec is definitely wrong -- I tried it for `x86_64-pc-windows-gnu`, which enables SSE3 that way. Building with `-Ctarget-feature=-sse3` works fine, and `cfg!(target_feature = "sse3")` is `false` in that build. There are also some indications that these are actually intended to be overwritten: `3b14526cea/compiler/rustc_target/src/spec/targets/i686_unknown_uefi.rs (L22-L23)` `84ac80f192/compiler/rustc_target/src/spec/targets/x86_64h_apple_darwin.rs (L18-L23)` So... let's update the comment to match reality, I guess? The claim that they overwrite `-Ctarget-cpu` is based on - for `native`, the comment in the apple target spec quoted above - for other CPU strings, the assumption that `LLVMRustCreateTargetMachine` will apply these features after doing whatever the base CPU model does. I am not sure how to check that, I hope some LLVM backend people can chime in. :)		2024-09-03 19:13:25 +02:00
..
src	Rollup merge of #129863 - RalfJung:target-spec-features, r=wesleywiser	2024-09-03 19:13:25 +02:00
Cargo.toml	dedup object	2024-07-28 17:21:07 +03:00
README.md	Fix outdated crate names in compiler docs	2021-04-08 11:12:14 -05:00

rustc_target contains some very low-level details that are specific to different compilation targets and so forth.

For more information about how rustc works, see the rustc dev guide.