about summary refs log tree commit diff
path: root/compiler/rustc_codegen_llvm/src
diff options
context:
space:
mode:
authorJubilee Young <workingjubilee@gmail.com>2025-06-16 12:07:24 -0700
committerJubilee Young <workingjubilee@gmail.com>2025-06-16 12:43:36 -0700
commit7b29a5d2827f4336ee2c3ca163378c9dc5a82238 (patch)
treed468d3e0ffdceb8ac58f370010bd3149691ee3f0 /compiler/rustc_codegen_llvm/src
parent3bc767e1a215c4bf8f099b32e84edb85780591b1 (diff)
downloadrust-7b29a5d2827f4336ee2c3ca163378c9dc5a82238.tar.gz
rust-7b29a5d2827f4336ee2c3ca163378c9dc5a82238.zip
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 everyone
uses `--print native-static-lib` correctly can be just a nuisance.

This reverts the following commits:
- f66787a08d57dc1296619b314d2be596085bfeef
- 72a9219e82c157041bfc8dfd378c9cb2b09c0650
- 98bb597c05c32365abbd6898f278b097352774ed
- c59b70841c36277464b51161e3fcf12dfcb667e0

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')
0 files changed, 0 insertions, 0 deletions