-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Raw pointer alignment checks in debug #570
Comments
This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed. cc @rust-lang/compiler @rust-lang/compiler-contributors |
@rustbot second |
I love this! |
I'm nominated this for discussion in the lang team meeting: these sorts of user-visible changes feel like sometimes we ought to discuss. That said, I personally have long wanted us to make debug builds more effective at detecting UB, and I approve of steps in that direction. |
@rustbot label -final-comment-period +major-change-accepted |
Proposal
Add a MIR transform which inserts an explicit check that a raw pointer is aligned before it is dereferenced, panicking if it isn't. This transform should only be run when debug assertions are enabled.
I have been slowly working on a draft implementation: rust-lang/rust#98112
See also: rust-lang/rust#54915 rust-lang/rust#51713
Mentors or Reviewers
@oli-obk has lightly committed to reviewing the existing implementation
Process
The main points of the Major Change Process are as follows:
@rustbot second
.-C flag
, then full team check-off is required.@rfcbot fcp merge
on either the MCP or the PR.You can read more about Major Change Proposals on forge.
Comments
This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.
The text was updated successfully, but these errors were encountered: