Closed SparrowLii closed 11 months ago
I also found this in r/rust. I thought this is a bug of zig at that time, but now I find it's a regression of rust.
Test with the config in my reply
> cargo bisect-rustc --verbose --with-src --start 2021-01-01
...
searched toolchains nightly-2021-01-01 through nightly-2021-10-29
********************************************************************************
Regression in nightly-2021-10-05
********************************************************************************
...
get_commits_between returning commits, len: 7
commit[0] 2021-10-03UTC: Auto merge of #89486 - rusticstuff:docker_letsencrypt_ca_update, r=Mark-Simulacrum
commit[1] 2021-10-03UTC: Auto merge of #88175 - camsteffen:let-desugar-span, r=Manishearth
commit[2] 2021-10-04UTC: Auto merge of #89165 - jkugelman:read-to-end-overallocation, r=joshtriplett
commit[3] 2021-10-04UTC: Auto merge of #89512 - Manishearth:rollup-meh9x7r, r=Manishearth
commit[4] 2021-10-04UTC: Auto merge of #89489 - FabianWolff:issue-89485, r=oli-obk
commit[5] 2021-10-04UTC: Auto merge of #88834 - the8472:char-count, r=joshtriplett
commit[6] 2021-10-04UTC: Auto merge of #89530 - workingjubilee:rollup-ua14iq6, r=workingjubilee
validated commits found, specifying toolchains
...
********************************************************************************
Regression in 003d8d3f56848b6f3833340e859b089a09aea36a
********************************************************************************
So It's pr https://github.com/rust-lang/rust/pull/83655 via https://github.com/rust-lang/rust/commit/003d8d3f56848b6f3833340e859b089a09aea36a
It also cause another breakage: https://github.com/rust-lang/rust/issues/89626
This problem can currently be solved by adding the compilation parameter -Ctarget-feature=-outline-atomics
, so I think this issue can be closed.
I'm going to reopen. We want build-std to "just work", and not working on a tier-1 platform without a special option isn't the kind of experience we would like.
I'm still uncertain about the solution here. I don't want to hard-code special rules inside cargo. I also don't want to require building C code. I don't yet fully understand this situation, though. rust-lang/rust#83655 contains some more discussion.
This was a mistake on my part, my apologies. It will be corrected.
This will be fixed by https://github.com/rust-lang/rust/pull/102579.
https://github.com/rust-lang/rust/pull/113269 has landed :)
Ah, thank you so much!
My
main.rs
:My
Cargo.toml
:My rust version:
My cargo version:
And when I run
cargo +nightly build -Z build-std=std,panic_abort --target aarch64-unknown-linux-gnu --release
, it failed as following:Is this because the build-std tool does not support aarch64?