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.
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
[mir-opt] GVN some more transmute cases #133324
[mir-opt] GVN some more transmute cases #133324
Changes from all commits
8dcc676
259c425
03650dd
293f8e8
b421a56
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we gate this on
self.type_may_have_niche_of_interest_to_backend(from)
? It seems we lose information when transmuting from aNonNull
aggregate.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting point!
alloca
s in codegen for simplemir::Aggregate
statements #123886, but even before that when we had thealloca
there still wasn't any!nonnull
metadata anywhere: https://rust.godbolt.org/z/xoj1G4WWj#[repr(transparent)] struct MyBool(bool);
isn't something we need to do despite that type having an interesting niche in itsScalar
.[rustc_layout_scalar_valid_range_*]
types compiler-team#807 -style proposal to also banAggregate
ing arustc_layout_scalar_valid_range_*
type, and requireTransmute
ing to it instead. That way the niche would be asserted on construction too, not just on read. (Of course, the library could also choose to use transmute without such an MCP requiring it.)