[clubby789]

While investigating another issue, I noticed that there were a lot of unstable features with incorrect or outdated links to their tracking issues.

[rustbot]

Some changes occurred in library/core/src/intrinsics/gpu.rs

cc @Flakebi

Some changes occurred in src/doc/unstable-book/src/compiler-flags/control-flow-guard.md

cc @rust-lang/project-exploit-mitigations, @rcvalle

Some changes occurred to the intrinsics. Make sure the CTFE / Miri interpreter
gets adapted for the changes, if necessary.

cc @rust-lang/miri, @RalfJung, @oli-obk, @lcnr

[rustbot]

r? @mejrs

rustbot has assigned @mejrs.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

• Owners of files modified in this PR: compiler
• compiler expanded to 77 candidates
• Random selection from 20 candidates

[clubby789]

While I removed this as the flag is stablised, there's a lot of information here which AFAICT isn't reflected in stable documentation. It might be a good idea to find a new home for it

View changes since the review

[mejrs]

It exists here: https://doc.rust-lang.org/rustc/codegen-options/index.html#control-flow-guard

(with a link to microsoft's docs, which are a little more in depth than the above link)

[clubby789]

More so the notes on interop, 'when to use', 'testing', 'libraries' (the Rust specific stuff), which don't seem to be present otherwise.

[mejrs]

Can you find a new place for the control flow guard information? Or if not, file an issue so it's not lost?

@bors r+ rollup

View changes since this review

[rust-bors]

📌 Commit 23deb45 has been approved by mejrs

It is now in the queue for this repository.