Rust 1.45.0 aarch64-apple-ios generates multiple messages: "'+cyclone' is not a recognized feature for this target (ignoring feature)"

[trsoluti]

I tried this code:

cargo new cyclone_test
cd cyclone_test
cargo build --target=aarch64-apple-ios

I expected to see this happen: explanation
no errors or warnings
Instead, this happened: explanation
multiple copies of

'+cyclone' is not a recognized feature for this target (ignoring feature)

Meta

rustc --version --verbose:

rustc 1.45.0 (5c1f21c3b 2020-07-13)
binary: rustc
commit-hash: 5c1f21c3b82297671ad3ae1e8c942d2ca92e84f2
commit-date: 2020-07-13
host: x86_64-apple-darwin
release: 1.45.0
LLVM version: 10.0

Backtrace

(not applicable)

[tesuji]

"cyclone" has been renamed to "apple-a7" in #73086 .

[tesuji]

ping @Mark-Simulacrum

[trevyn]

This is fixed in beta and nightly via #73086. Should probably be nominated for backport to a point release, if there is one.

[francesca64]

Is this fixed in 1.45.1?

[Mark-Simulacrum]

I am confused how it was fixed in beta and nightly by #73086, as it seems that was not backported to beta.

@lzutao -- please ping the whole release team, not just me, so that hopefully someone sees things like this. It would also be helpful to include some mention about why you're pinging rather than just doing so.

This was not fixed in 1.45.1. I am not sure that I am inclined to backport it into stable at all, though, presuming that it is merely an annoyance rather than an error?

[francesca64]

@Mark-Simulacrum

presuming that it is merely an annoyance rather than an error?

#73086 (comment) suggests that it "probably also created incorrectly optimized artifacts", though things indeed still build fine. That said, this does result in a lot of messages, i.e. in a largish project I'm seeing it 719 times, which makes it difficult to read any other build output. So at the very least, it's a substantial user experience regression.

[JohnTitor]

Removing I-prioritize as this is waiting on backport (but it seems we missed it on 1.45.2?) and already fixed in beta and nightly (related discussion on the wg-prioritization).

[spastorino]

@Mark-Simulacrum I think we should close this issue given that we decided to not backport to stable, right?.

[Mark-Simulacrum]

Given that it's fixed on beta/nightly that does indeed seem reasonable.