about summary refs log tree commit diff
path: root/compiler/rustc_codegen_gcc
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2025-01-27 03:57:37 +0000
committerbors <bors@rust-lang.org>2025-01-27 03:57:37 +0000
commit633a3fe36dd9a5196054dc3a61adbd3c61854dcf (patch)
treee28935fd8ea698667f7b1fca8d672a4573c8cc81 /compiler/rustc_codegen_gcc
parent0df0662ee06bb8987e0cdbfae5634b1630d41236 (diff)
parent2f4dd6e6890eefe30b4c041486ec3af90a071eb2 (diff)
downloadrust-633a3fe36dd9a5196054dc3a61adbd3c61854dcf.tar.gz
rust-633a3fe36dd9a5196054dc3a61adbd3c61854dcf.zip
Auto merge of #135937 - bjorn3:separate_coretests_crate, r=jieyouxu,tgross35
Put the core unit tests in a separate coretests package

Having standard library tests in the same package as a standard library crate has bad side effects. It causes the test to have a dependency on a locally built standard library crate, while also indirectly depending on it through libtest. Currently this works out fine in the context of rust's build system as both copies are identical, but for example in cg_clif's tests I've found it basically impossible to compile both copies with the exact same compiler flags and thus the two copies would cause lang item conflicts.

This PR moves the tests of libcore to a separate package which doesn't depend on libcore, thus preventing the duplicate crates even when compiler flags don't exactly match between building the sysroot (for libtest) and building the test itself. The rest of the standard library crates do still have this issue however.
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions