Skip to content

miri recursive validation: only check one layer deep#154269

Open
RalfJung wants to merge 1 commit intorust-lang:mainfrom
RalfJung:miri-recursive-shallow
Open

miri recursive validation: only check one layer deep#154269
RalfJung wants to merge 1 commit intorust-lang:mainfrom
RalfJung:miri-recursive-shallow

Conversation

@RalfJung
Copy link
Member

@RalfJung RalfJung commented Mar 23, 2026

As has been proposed in rust-lang/unsafe-code-guidelines#414, let's see what happens if we make recursive checking in Miri shallow: we treat whatever is behind a reference as if it was inside MaybeDangling, which means nested references do not have to be dereferenceable.

This changes the meaning of the original flag -- I don't think it is worth supporting multiple variants of recursive checking (it'd require a bunch of new plumbing), and this seems to be the strictest variant that still has any traction in the discussion.

@rustbot rustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Mar 23, 2026
@RalfJung
Copy link
Member Author

@bors try jobs=dist-x86_64-linux

@rust-bors

This comment has been minimized.

rust-bors bot pushed a commit that referenced this pull request Mar 23, 2026
miri recursive checking: only check one layer deep


try-job: dist-x86_64-linux
@RalfJung RalfJung force-pushed the miri-recursive-shallow branch from 3b4979d to 54efd74 Compare March 23, 2026 17:43
@RalfJung
Copy link
Member Author

@bors try jobs=dist-x86_64-linux

@rust-bors

This comment has been minimized.

rust-bors bot pushed a commit that referenced this pull request Mar 23, 2026
miri recursive checking: only check one layer deep


try-job: dist-x86_64-linux
@RalfJung RalfJung force-pushed the miri-recursive-shallow branch from 54efd74 to eac975c Compare March 23, 2026 19:23
@RalfJung RalfJung changed the title miri recursive checking: only check one layer deep miri recursive validation: only check one layer deep Mar 23, 2026
@rust-bors
Copy link
Contributor

rust-bors bot commented Mar 23, 2026

☀️ Try build successful (CI)
Build commit: 5b0348a (5b0348a8cd8ae08dde6362cefc4cb3b6c78329e3, parent: 13e2abaac846b2680ae93e1b3bd9fe7fe1b9a7fe)

@RalfJung RalfJung force-pushed the miri-recursive-shallow branch from eac975c to 5f68044 Compare March 24, 2026 06:59
@RalfJung RalfJung marked this pull request as ready for review March 24, 2026 06:59
@rustbot
Copy link
Collaborator

rustbot commented Mar 24, 2026

The Miri subtree was changed

cc @rust-lang/miri

Some changes occurred to the CTFE / Miri interpreter

cc @rust-lang/miri

Some changes occurred to the CTFE machinery

cc @oli-obk, @lcnr

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Mar 24, 2026
@rustbot rustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Mar 24, 2026
@rustbot
Copy link
Collaborator

rustbot commented Mar 24, 2026

r? @petrochenkov

rustbot has assigned @petrochenkov.
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, mir
  • compiler, mir expanded to 69 candidates
  • Random selection from 12 candidates

@RalfJung
Copy link
Member Author

This is basically a tweak of #128531.
r? @saethlin

@rustbot rustbot assigned saethlin and unassigned petrochenkov Mar 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants