Skip to content

Conversation

@Zalathar
Copy link
Contributor

This "cleanup" function is more than a decade old, and I can't find any evidence of modern-day bootstrap being able to pass any of these flags to --host-rustcflags or --target-rustcflags.

I thought about replacing the cleanup with an assertion, but I think it's better to delete it entirely for now, and re-add checks later if they're motivated by actual problems in practice.

In addition to deleting some old and confusing code, this also lets us remove three instances of duplicating TestCx, which is the biggest win.

r? jieyouxu

This "cleanup" function is more than a decade old, and I can't find any
evidence of modern-day bootstrap being able to pass any of these flags to
`--host-rustcflags` or `--target-rustcflags`.
@rustbot
Copy link
Collaborator

rustbot commented Oct 28, 2025

Some changes occurred in src/tools/compiletest

cc @jieyouxu

@rustbot rustbot added A-compiletest Area: The compiletest test runner A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) labels Oct 28, 2025
@rustbot
Copy link
Collaborator

rustbot commented Oct 28, 2025

jieyouxu is currently at their maximum review capacity.
They may take a while to respond.

@Zalathar
Copy link
Contributor Author

Some relevant ancient commits introducing the removed code:

@Zalathar
Copy link
Contributor Author

@bors try jobs=x86_64-msvc-1,i686-msvc-1,aarch64-msvc-1,x86_64-mingw-1,test-various,armhf-gnu,aarch64-apple

@rust-bors

This comment has been minimized.

rust-bors bot added a commit that referenced this pull request Oct 28, 2025
compiletest: Remove `cleanup_debug_info_options`

try-job: x86_64-msvc-1
try-job: i686-msvc-1
try-job: aarch64-msvc-1
try-job: x86_64-mingw-1
try-job: test-various
try-job: armhf-gnu
try-job: aarch64-apple
@Zalathar
Copy link
Contributor Author

jieyouxu is currently at their maximum review capacity.
They may take a while to respond.

I have a few more compiletest PRs that I plan to open (big and small), so I understand if it takes some time to get around to all of them. Thanks for your good work! 💖

@rust-bors
Copy link

rust-bors bot commented Oct 28, 2025

☀️ Try build successful (CI)
Build commit: 5bf34a8 (5bf34a8252ab0d62acaeddf7a02112f90f7d9dbc, parent: adaa838976ff99a4f0661136322f64cb466b58a0)

@jieyouxu
Copy link
Member

I have a few more compiletest PRs that I plan to open (big and small), so I understand if it takes some time to get around to all of them. Thanks for your good work! 💖

Yeah that is perfectly fine, it'll just take some time for me to get through them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-compiletest Area: The compiletest test runner A-testsuite Area: The testsuite used to check the correctness of rustc S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants