Make run-make testsuite work with other codegen backend than LLVM - #162482
Conversation
|
|
|
Ah, let's set someone else then. r? @Kobzol |
|
|
e29a8ed to
5dffd45
Compare
|
Updated. |
|
Thanks, looks good. @bors r+ |
…r=Kobzol Make `run-make` testsuite work with other codegen backend than LLVM Needed for rust-lang#159924. Currently, we always run `run-make` testsuite with the codegen backend rustc was compiled with. However, in CI it's compiled with LLVM, so when we want to test with GCC (with `--test-codegen-backend`), it compiles `rmake.rs` with the GCC backend, but when running the test, it doesn't use the GCC backend since it just calls `rustc`. So to get around that, I now pass the codegen backend through the environment and set it in the `rustc` function of `run_make_support`. To be noted that for now it's only for the `rustc` function, no other command uses it. Should I extend it right away for all commands (well, likely only `cargo`) or just `rustc` for now is enough? r? @jieyouxu
|
Seems like I need to fix some tests first. :') @bors r- |
|
This pull request was unapproved. This PR was contained in a rollup (#162486), which was unapproved. |
f6683e8 to
8d586e7
Compare
|
We still have quite a few tests we need to fix in the GCC backend. For now, I marked them as ignored for the GCC backend. But it's nice since we have a new list of regression tests we'll be able to use. =D |
|
Why only some tests have FIXMEs, the others are LLVM only? Anyway, feel free to r=me once PR CI is green :) |
This comment has been minimized.
This comment has been minimized.
Because the ones with the llvm components, I'm not sure they're relevant for gcc backend. |
… works for them Limit some `run-make` tests to LLVM until GCC backend works for them
8d586e7 to
21cfbad
Compare
|
Seems like CI is happy, let's go. =D @bors r=Kobzol |
…r=Kobzol Make `run-make` testsuite work with other codegen backend than LLVM Needed for rust-lang#159924. Currently, we always run `run-make` testsuite with the codegen backend rustc was compiled with. However, in CI it's compiled with LLVM, so when we want to test with GCC (with `--test-codegen-backend`), it compiles `rmake.rs` with the GCC backend, but when running the test, it doesn't use the GCC backend since it just calls `rustc`. So to get around that, I now pass the codegen backend through the environment and set it in the `rustc` function of `run_make_support`. To be noted that for now it's only for the `rustc` function, no other command uses it. Should I extend it right away for all commands (well, likely only `cargo`) or just `rustc` for now is enough? r? @jieyouxu
Rollup of 6 pull requests Successful merges: - #162482 (Make `run-make` testsuite work with other codegen backend than LLVM) - #161587 (Avoid invalid suggestion in case of macro expansion without inferrable generic type) - #162363 (Use correct `dir_path` when parsing module from path) - #162408 (add crashtests [7/N]) - #162502 (triagebot: Subscribe me to amdgpu changes) - #162505 (Revert "fuchsia: Add safestack as a supported sanitizer for x86_64 fuchsia")
Rollup merge of #162482 - GuillaumeGomez:run-make-backends, r=Kobzol Make `run-make` testsuite work with other codegen backend than LLVM Needed for #159924. Currently, we always run `run-make` testsuite with the codegen backend rustc was compiled with. However, in CI it's compiled with LLVM, so when we want to test with GCC (with `--test-codegen-backend`), it compiles `rmake.rs` with the GCC backend, but when running the test, it doesn't use the GCC backend since it just calls `rustc`. So to get around that, I now pass the codegen backend through the environment and set it in the `rustc` function of `run_make_support`. To be noted that for now it's only for the `rustc` function, no other command uses it. Should I extend it right away for all commands (well, likely only `cargo`) or just `rustc` for now is enough? r? @jieyouxu
Needed for #159924.
Currently, we always run
run-maketestsuite with the codegen backend rustc was compiled with. However, in CI it's compiled with LLVM, so when we want to test with GCC (with--test-codegen-backend), it compilesrmake.rswith the GCC backend, but when running the test, it doesn't use the GCC backend since it just callsrustc. So to get around that, I now pass the codegen backend through the environment and set it in therustcfunction ofrun_make_support.To be noted that for now it's only for the
rustcfunction, no other command uses it. Should I extend it right away for all commands (well, likely onlycargo) or justrustcfor now is enough?r? @jieyouxu