-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bootstrap: support target specific config overrides #125515
Conversation
Debug, PartialEq, and Eq are derived for testing purposes.
rustbot has assigned @albertlarsan68. Use |
This PR modifies If appropriate, please update |
This doesn't really change any schema of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't really change any schema of config.toml, so probably don't need to update? Not sure though.
Yeah, update isn't needed for this.
Feel free to r=me once the CI is green. r? onur-ozkan |
Thanks for the review! @bors r=onur-ozkan rollup |
…onur-ozkan bootstrap: support target specific config overrides Can't find any previous discussion about not supporting this, so I get it done. The motivation of this is from <rust-lang#125473 (comment)>.
…kingjubilee Rollup of 9 pull requests Successful merges: - rust-lang#124080 (Some unstable changes to where opaque types get defined) - rust-lang#125271 (use posix_memalign on almost all Unix targets) - rust-lang#125433 (A small diagnostic improvement for dropping_copy_types) - rust-lang#125498 (Stop using the avx512er and avx512pf x86 target features) - rust-lang#125510 (remove proof tree formatting, make em shallow) - rust-lang#125513 (Don't eagerly monomorphize drop for types that are impossible to instantiate) - rust-lang#125514 (Structurally resolve before `builtin_index` in EUV) - rust-lang#125515 ( bootstrap: support target specific config overrides ) - rust-lang#125527 (Add manual Sync impl for ReentrantLockGuard) r? `@ghost` `@rustbot` modify labels: rollup
This is the only one that seems like it can explain the failure in but I still don't know how... @bors rollup=iffy |
@workingjubilee I don't think it's this PR fault that the rollup failed. The more likely explanation given the source code is #125433. |
It certainly seems so. My PR would check fn main() { let mut x = 3; drop(x); } Where should the repairs be made to make them suitable? |
In the Cargo repository, by submitting a PR fixing the test https://github.com/rust-lang/cargo/blob/a8d72c675ee52dd57f0d8f2bae6655913c15b2fb/tests/testsuite/fix.rs#L504-L545 |
…ur-ozkan bootstrap: support target specific config overrides Can't find any previous discussion about not supporting this, so I get it done. The motivation of this is from <rust-lang#125473 (comment)>.
A job failed! Check out the build log: (web) (plain) Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
Seems like a temporary network problem. @bors retry |
@Urgau Oh. Why don't we run that test in the PR CI...? |
☀️ Test successful - checks-actions |
It checks too much stuff I guess? These are additional stuff we need to test rust/src/bootstrap/mk/Makefile.in Lines 50 to 82 in 606afbb
|
Finished benchmarking commit (1ba35e9): comparison URL. Overall result: ❌ regressions - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesResults (secondary -3.0%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 671.029s -> 672.69s (0.25%) |
Can't find any previous discussion about not supporting this,
so I get it done.
The motivation of this is from #125473 (comment).