about summary refs log tree commit diff
path: root/compiler/rustc_codegen_llvm/src/common.rs
diff options
context:
space:
mode:
authorJubilee <workingjubilee@gmail.com>2025-06-17 00:28:20 -0700
committerGitHub <noreply@github.com>2025-06-17 00:28:20 -0700
commit99c8475e529bfbaf738b12276431fe14d2e98bc3 (patch)
tree9bc45b6ba8f75ab24b16aee23ace4078590534a2 /compiler/rustc_codegen_llvm/src/common.rs
parent5df238921f705b1022564f0aac2f76898059413b (diff)
parent7b29a5d2827f4336ee2c3ca163378c9dc5a82238 (diff)
downloadrust-99c8475e529bfbaf738b12276431fe14d2e98bc3.tar.gz
rust-99c8475e529bfbaf738b12276431fe14d2e98bc3.zip
Rollup merge of #142595 - workingjubilee:revert-warning-138139, r=ChrisDenton
Revert overeager warning for misuse of `--print native-static-libs`

In a PR to emit warnings on misuse of `--print native-static-libs`, we did not consider the matter of composing parts of build systems. If you are not directly invoking rustc, it can be difficult to know when you will in fact compile a staticlib, so making sure uses `--print native-static-lib` correctly can be just a nuisance.

Next cycle we can reland a slightly more narrowly focused variant or one that focuses on `--emit` instead of `--print native-static-libs`. But in its current state, I am not sure the warning is very useful.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/common.rs')
0 files changed, 0 insertions, 0 deletions