[beta] stage0 bump + backports

[Mark-Simulacrum]

This bumps stage0 (https://forge.rust-lang.org/release/process.html#beta-stage0-update-friday), and backports:

• Revert "Rollup merge of std::thread::available_parallelism merging linux/android/freebsd version #120589 - devnexen:cpuaff_fbsd_upd, r=clarfonthey" - Revert "Rollup merge of #120589 - devnexen:cpuaff_fbsd_upd, r=clarfonthey" #163498
• Clarify some things in the docs of Global - Clarify some things in the docs of Global #163401

r? me

[rustbot]

⚠️ Warning ⚠️

• There are issue links (such as #123) in the commit messages of the following commits.
  Please move them to the PR description, to avoid spamming the issues with references to the commit, and so this bot can automatically canonicalize them to avoid issues with subtrees.
  • b4ed9db

[Mark-Simulacrum]

@bors r+ rollup=never

[rust-bors]

📌 Commit 4da72b5 has been tentatively approved by Mark-Simulacrum

It will be put into the queue for this repository once PR CI succeeds.

[rust-log-analyzer]

The job test-aarch64-apple-macos-26-1 failed! Check out the build log: (web) (plain enhanced) (plain)

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

Important

For more information how to resolve CI failures of this job, visit this link.

[rust-bors]

💔 Test for ea3745a failed: CI. Failed job:

• auto - test-aarch64-apple-macos-26-1 (web logs, enhanced plaintext logs)

[theemathas]

The failing test was added in #158807. cc @Vastargazing (author), @RalfJung (reviewer)

[theemathas]

Maybe the test is flaky?

@bors try test-aarch64-apple-macos-26-1

[rust-bors]

Unknown argument "test-aarch64-apple-macos-26-1". Did you mean to use @bors jobs=<jobs>|parent=<parent>? Run @bors help or go to https://bors.rust-lang.org/help to see available commands.

[theemathas]

@bors try jobs=test-aarch64-apple-macos-26-1

[RalfJung]

The test passes in Miri, so it should be fine, but ofc it could uncover bugs elsewhere.

That said, the test is a tricky one, with what it assumes about which allocations happen where. It just seems odd that it would only fail on the beta branch...
It almost seems like the custom allocator is actually used outside Miri (which #158807 said it wouldn't -- I don't know the details to judge what's true; Cc @bjorn3 ), and then the panic doesn't get caught properly for some reason.

[rust-bors]

☀️ Try build successful (CI)
Build commit: 1e10d39 (1e10d39074091bcb8fe3d01dc7ebff8a449b611e)
Base parent: 7bbda45 (7bbda45cb1ec0a378d91959646a8fa904be3192a)

[theemathas]

I assume the test was somehow flaky

@bors r=Mark-Simulacrum rollup=never

[rust-bors]

📌 Commit 4da72b5 has been approved by Mark-Simulacrum

It is now in the queue for this repository.

A failed build status on this PR was cleared due to the approval.

[rust-bors]

☀️ Test successful - CI
Approved by: Mark-Simulacrum
Duration: 2h 56m 18s
Pushing a2eb609 to beta...