Destabilize cfg(target_has_atomic_load_store = ...)

[Mark-Simulacrum]

This was not intended to be stabilized yet.

This keeps the cfg_target_has_atomic feature gate name since compiler-builtins otherwise depends on it and I'd rather not try to manage a bump across a crates.io published repository given the time-sensitivity here (we need to land this quickly to avoid a beta backport).

Closes #32976

r? @Amanieu

[Mark-Simulacrum]

Bumped with a version that re-uses the old cfg_target_has_atomic gate to avoid the compiler-builtins failure.

[Amanieu]

r=me once CI failure is fixed.

[Mark-Simulacrum]

@bors r=Amanieu p=1 (needed before beta branch on Friday)

[bors]

📌 Commit fc01d2b has been approved by Amanieu

[bors]

⌛ Testing commit fc01d2b with merge 02e9008ac62b70bd28e538eb5f519876c10d0b24...

[rust-log-analyzer]

The job armhf-gnu failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)

---- [ui] ui/issues/issue-42210.rs stdout ----

error: test run failed!
status: exit status: 101
command: "/checkout/obj/build/x86_64-unknown-linux-gnu/stage0-tools-bin/remote-test-client" "run" "0" "/checkout/obj/build/x86_64-unknown-linux-gnu/test/ui/issues/issue-42210/a"
------------------------------------------
uploaded "/checkout/obj/build/x86_64-unknown-linux-gnu/test/ui/issues/issue-42210/a", waiting for result

------------------------------------------
------------------------------------------
stderr:
------------------------------------------
thread 'main' panicked at 'client.read_exact(&mut header) failed with Connection reset by peer (os error 104)', src/tools/remote-test-client/src/main.rs:310:9

------------------------------------------

[bors]

💔 Test failed - checks-actions

[Mark-Simulacrum]

@bors retry

'client.read_exact(&mut header) failed with Connection reset by peer (os error 104)', src/tools/remote-test-client/src/main.rs:310:9

[bors]

⌛ Testing commit fc01d2b with merge 930fc4f...

[bors]

☀️ Test successful - checks-actions
Approved by: Amanieu
Pushing 930fc4f to master...

[rust-timer]

Finished benchmarking commit (930fc4f): comparison url.

Summary: This benchmark run did not return any relevant results.

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

@rustbot label: -perf-regression