Repository navigation
Add safety sections to xrstor-family restore intrinsics - #2251
Open
kiana1kaslana wants to merge 1 commit into
Open
kiana1kaslana wants to merge 1 commit into
kiana1kaslana wants to merge 1 commit into
Conversation
Collaborator
|
Thanks for the pull request, and welcome! The Rust Project has assigned @sayantn (or someone else) to review your changes, you should hear from them (or someone else) within the next two weeks. Why was this reviewer chosen?The reviewer was selected based on:
|
kiana1kaslana
force-pushed
the
safety-doc-xrstor
branch
from
October 11, 2026 09:24
9a6c7db to
21ee2e2
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
_xrstor, _xrstors and their 64-bit variants are declared unsafe but carry no # Safety section. This adds the missing sections.
These instructions read back an XSAVE area written by a prior save, so the sections require mem_addr to be valid for reads of the whole area it describes and to be 64-byte aligned, and the memory to contain a valid XSAVE area matching the format in the referenced Intel SDM section.
Doc-only change.