Skip to content

[mir-opt] Allow SRoA when an object is transmuted to a field type - #158291

Closed
scottmcm wants to merge 1 commit into
rust-lang:mainfrom
scottmcm:even-better-read-unaligned
Closed

[mir-opt] Allow SRoA when an object is transmuted to a field type#158291
scottmcm wants to merge 1 commit into
rust-lang:mainfrom
scottmcm:even-better-read-unaligned

Conversation

@scottmcm

@scottmcmscottmcm commented Jun 23, 2026

Copy link
Copy Markdown
Member

Inspired by #158202 (comment), this allows SRoA to expand a local consumed by a CastKind::Transmute if that transmute is to the type of a field, since if it's to the type of a field we can just have it take the local for that field like we would if it was a field projection.

Future PRs could do more complex stuff, like using layout to always allow SRoA of x in Transmute(x) when x is https://doc.rust-lang.org/nightly/nightly-rustc/rustc_middle/ty/layout/type.TyAndLayout.html#method.non_1zst_field, but this is enough for the specific case I needed.

r? mir-opt

@rustbot

Copy link
Copy Markdown
Collaborator

Some changes occurred to MIR optimizations

cc @rust-lang/wg-mir-opt

@rustbotrustbot added 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. labels Jun 23, 2026
@scottmcmscottmcm added the A-mir-opt Area: MIR optimizations label Jun 24, 2026
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Jul 1, 2026
…d, r=aapoalas
Implement `ptr::{read,write}_unaligned` via `repr(packed)`
We already support doing unaligned reads & writes via `repr(packed)` fields, so this just uses that support from the backend rather than needing to thinks about `memcpy` and `intrinsics::forget` and such.
Turns out in codegen this ends up essentially identical because the packed type read gets `BackendRepr::Memory` and thus the read/write of the packed type *is* an `align 1` memcpy, just like the library code before this PR. But doing this gives much simpler MIR and rust-lang#158291 will make it better than the previous version by not needing to emit the `memcpy` at all for things like `read_unaligned::<u32>`.
First commit are some tests that pass on master; Second commit changes the implementation and shows the corresponding test changes.
r? libs
jhpratt added a commit to jhpratt/rust that referenced this pull request Jul 1, 2026
…d, r=aapoalas
Implement `ptr::{read,write}_unaligned` via `repr(packed)`
We already support doing unaligned reads & writes via `repr(packed)` fields, so this just uses that support from the backend rather than needing to thinks about `memcpy` and `intrinsics::forget` and such.
Turns out in codegen this ends up essentially identical because the packed type read gets `BackendRepr::Memory` and thus the read/write of the packed type *is* an `align 1` memcpy, just like the library code before this PR. But doing this gives much simpler MIR and rust-lang#158291 will make it better than the previous version by not needing to emit the `memcpy` at all for things like `read_unaligned::<u32>`.
First commit are some tests that pass on master; Second commit changes the implementation and shows the corresponding test changes.
r? libs
@scottmcm
scottmcmforce-pushed the even-better-read-unaligned branch from 7ed426a to fd33c1fCompareJuly 2, 2026 05:30
@rustbot

Copy link
Copy Markdown
Collaborator

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

@scottmcm
scottmcmforce-pushed the even-better-read-unaligned branch from fd33c1f to a576ef9CompareJuly 2, 2026 05:35
Comment on lines -42 to +41
StorageLive(_4);
_4 = copy (*_3);
_5 = copy _4 as T (Transmute);
StorageDead(_4);
_4 = copy ((*_3).0: T);

@scottmcmscottmcmJul 2, 2026

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The library change to use packed landed in #158427, so now this shows the critical change from this optimization...

View changes since the review

Comment on lines -25 to +26
// CHECK-NOT: !noundef
// CHECK-NOT: !range
// CHECK-SAME: !range [[R16:![0-9]+]]
// CHECK-SAME: !noundef

@scottmcmscottmcmJul 2, 2026

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

...which then means these loads get metadata on them without codegen changes.

View changes since the review

@scottmcm

Copy link
Copy Markdown
MemberAuthor

The more I poked at this the less I'm confident that SRoA is the correct answer here, especially since I tried going a bit further and ended up just getting things like this

 bb0: {
StorageLive(_3);
_3 = PtrMetadata(copy _1);
StorageLive(_5);
StorageLive(_4);
_4 = &raw const (*_1);
- _5 = copy _4 as std::ptr::NonNull<[T]> (Transmute);+ _5 = copy _4 as (*const [T]) is !null (Transmute);
StorageDead(_4);
StorageLive(_7);
StorageLive(_6);
_6 = copy _5 as *mut [T] (Transmute);
_7 = copy _6 as *mut T (PtrToPtr);
StorageDead(_6);
- _8 = copy _7 as std::ptr::NonNull<T> (Transmute);+ _8 = copy _7 as (*const T) is !null (Transmute);
StorageDead(_7);
StorageDead(_5);
switchInt(const <T as std::mem::SizedTypeProperties>::IS_ZST) -> [0: bb1, otherwise: bb2];
}

which is kinda the opposite of the direction in #153085 which I think would be nicer to see when reading the MIR.

@scottmcm
scottmcm marked this pull request as draft July 3, 2026 11:18
@rustbotrustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jul 3, 2026
@scottmcm

Copy link
Copy Markdown
MemberAuthor

Closing this in favour of fixing the motivating example in layout instead, #159033

@scottmcmscottmcm closed this Jul 9, 2026
@rustbotrustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Jul 9, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-mir-optArea: MIR optimizationsT-compilerRelevant 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.

3 participants

@scottmcm@rustbot@saethlin
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
[mir-opt] Allow SRoA when an object is transmuted to a field type by scottmcm · Pull Request #158291 · rust-lang/rust · GitHub
Skip to content

[mir-opt] Allow SRoA when an object is transmuted to a field type - #158291

Closed
scottmcm wants to merge 1 commit into
rust-lang:mainfrom
scottmcm:even-better-read-unaligned
Closed

[mir-opt] Allow SRoA when an object is transmuted to a field type#158291
scottmcm wants to merge 1 commit into
rust-lang:mainfrom
scottmcm:even-better-read-unaligned

Conversation

@scottmcm

@scottmcmscottmcm commented Jun 23, 2026

Copy link
Copy Markdown
Member

Inspired by #158202 (comment), this allows SRoA to expand a local consumed by a CastKind::Transmute if that transmute is to the type of a field, since if it's to the type of a field we can just have it take the local for that field like we would if it was a field projection.

Future PRs could do more complex stuff, like using layout to always allow SRoA of x in Transmute(x) when x is https://doc.rust-lang.org/nightly/nightly-rustc/rustc_middle/ty/layout/type.TyAndLayout.html#method.non_1zst_field, but this is enough for the specific case I needed.

r? mir-opt

@rustbot

Copy link
Copy Markdown
Collaborator

Some changes occurred to MIR optimizations

cc @rust-lang/wg-mir-opt

@rustbotrustbot added 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. labels Jun 23, 2026
@scottmcmscottmcm added the A-mir-opt Area: MIR optimizations label Jun 24, 2026
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Jul 1, 2026
…d, r=aapoalas
Implement `ptr::{read,write}_unaligned` via `repr(packed)`
We already support doing unaligned reads & writes via `repr(packed)` fields, so this just uses that support from the backend rather than needing to thinks about `memcpy` and `intrinsics::forget` and such.
Turns out in codegen this ends up essentially identical because the packed type read gets `BackendRepr::Memory` and thus the read/write of the packed type *is* an `align 1` memcpy, just like the library code before this PR. But doing this gives much simpler MIR and rust-lang#158291 will make it better than the previous version by not needing to emit the `memcpy` at all for things like `read_unaligned::<u32>`.
First commit are some tests that pass on master; Second commit changes the implementation and shows the corresponding test changes.
r? libs
jhpratt added a commit to jhpratt/rust that referenced this pull request Jul 1, 2026
…d, r=aapoalas
Implement `ptr::{read,write}_unaligned` via `repr(packed)`
We already support doing unaligned reads & writes via `repr(packed)` fields, so this just uses that support from the backend rather than needing to thinks about `memcpy` and `intrinsics::forget` and such.
Turns out in codegen this ends up essentially identical because the packed type read gets `BackendRepr::Memory` and thus the read/write of the packed type *is* an `align 1` memcpy, just like the library code before this PR. But doing this gives much simpler MIR and rust-lang#158291 will make it better than the previous version by not needing to emit the `memcpy` at all for things like `read_unaligned::<u32>`.
First commit are some tests that pass on master; Second commit changes the implementation and shows the corresponding test changes.
r? libs
@scottmcm
scottmcmforce-pushed the even-better-read-unaligned branch from 7ed426a to fd33c1fCompareJuly 2, 2026 05:30
@rustbot

Copy link
Copy Markdown
Collaborator

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

@scottmcm
scottmcmforce-pushed the even-better-read-unaligned branch from fd33c1f to a576ef9CompareJuly 2, 2026 05:35
Comment on lines -42 to +41
StorageLive(_4);
_4 = copy (*_3);
_5 = copy _4 as T (Transmute);
StorageDead(_4);
_4 = copy ((*_3).0: T);

@scottmcmscottmcmJul 2, 2026

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The library change to use packed landed in #158427, so now this shows the critical change from this optimization...

View changes since the review

Comment on lines -25 to +26
// CHECK-NOT: !noundef
// CHECK-NOT: !range
// CHECK-SAME: !range [[R16:![0-9]+]]
// CHECK-SAME: !noundef

@scottmcmscottmcmJul 2, 2026

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

...which then means these loads get metadata on them without codegen changes.

View changes since the review

@scottmcm

Copy link
Copy Markdown
MemberAuthor

The more I poked at this the less I'm confident that SRoA is the correct answer here, especially since I tried going a bit further and ended up just getting things like this

 bb0: {
StorageLive(_3);
_3 = PtrMetadata(copy _1);
StorageLive(_5);
StorageLive(_4);
_4 = &raw const (*_1);
- _5 = copy _4 as std::ptr::NonNull<[T]> (Transmute);+ _5 = copy _4 as (*const [T]) is !null (Transmute);
StorageDead(_4);
StorageLive(_7);
StorageLive(_6);
_6 = copy _5 as *mut [T] (Transmute);
_7 = copy _6 as *mut T (PtrToPtr);
StorageDead(_6);
- _8 = copy _7 as std::ptr::NonNull<T> (Transmute);+ _8 = copy _7 as (*const T) is !null (Transmute);
StorageDead(_7);
StorageDead(_5);
switchInt(const <T as std::mem::SizedTypeProperties>::IS_ZST) -> [0: bb1, otherwise: bb2];
}

which is kinda the opposite of the direction in #153085 which I think would be nicer to see when reading the MIR.

@scottmcm
scottmcm marked this pull request as draft July 3, 2026 11:18
@rustbotrustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jul 3, 2026
@scottmcm

Copy link
Copy Markdown
MemberAuthor

Closing this in favour of fixing the motivating example in layout instead, #159033

@scottmcmscottmcm closed this Jul 9, 2026
@rustbotrustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Jul 9, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-mir-optArea: MIR optimizationsT-compilerRelevant 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.

3 participants

@scottmcm@rustbot@saethlin
, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' [mir-opt] Allow SRoA when an object is transmuted to a field type by scottmcm · Pull Request #158291 · rust-lang/rust · GitHub
Skip to content

[mir-opt] Allow SRoA when an object is transmuted to a field type - #158291

Closed
scottmcm wants to merge 1 commit into
rust-lang:mainfrom
scottmcm:even-better-read-unaligned
Closed

[mir-opt] Allow SRoA when an object is transmuted to a field type#158291
scottmcm wants to merge 1 commit into
rust-lang:mainfrom
scottmcm:even-better-read-unaligned

Conversation

@scottmcm

@scottmcmscottmcm commented Jun 23, 2026

Copy link
Copy Markdown
Member

Inspired by #158202 (comment), this allows SRoA to expand a local consumed by a CastKind::Transmute if that transmute is to the type of a field, since if it's to the type of a field we can just have it take the local for that field like we would if it was a field projection.

Future PRs could do more complex stuff, like using layout to always allow SRoA of x in Transmute(x) when x is https://doc.rust-lang.org/nightly/nightly-rustc/rustc_middle/ty/layout/type.TyAndLayout.html#method.non_1zst_field, but this is enough for the specific case I needed.

r? mir-opt

@rustbot

Copy link
Copy Markdown
Collaborator

Some changes occurred to MIR optimizations

cc @rust-lang/wg-mir-opt

@rustbotrustbot added 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. labels Jun 23, 2026
@scottmcmscottmcm added the A-mir-opt Area: MIR optimizations label Jun 24, 2026
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Jul 1, 2026
…d, r=aapoalas
Implement `ptr::{read,write}_unaligned` via `repr(packed)`
We already support doing unaligned reads & writes via `repr(packed)` fields, so this just uses that support from the backend rather than needing to thinks about `memcpy` and `intrinsics::forget` and such.
Turns out in codegen this ends up essentially identical because the packed type read gets `BackendRepr::Memory` and thus the read/write of the packed type *is* an `align 1` memcpy, just like the library code before this PR. But doing this gives much simpler MIR and rust-lang#158291 will make it better than the previous version by not needing to emit the `memcpy` at all for things like `read_unaligned::<u32>`.
First commit are some tests that pass on master; Second commit changes the implementation and shows the corresponding test changes.
r? libs
jhpratt added a commit to jhpratt/rust that referenced this pull request Jul 1, 2026
…d, r=aapoalas
Implement `ptr::{read,write}_unaligned` via `repr(packed)`
We already support doing unaligned reads & writes via `repr(packed)` fields, so this just uses that support from the backend rather than needing to thinks about `memcpy` and `intrinsics::forget` and such.
Turns out in codegen this ends up essentially identical because the packed type read gets `BackendRepr::Memory` and thus the read/write of the packed type *is* an `align 1` memcpy, just like the library code before this PR. But doing this gives much simpler MIR and rust-lang#158291 will make it better than the previous version by not needing to emit the `memcpy` at all for things like `read_unaligned::<u32>`.
First commit are some tests that pass on master; Second commit changes the implementation and shows the corresponding test changes.
r? libs
@scottmcm
scottmcmforce-pushed the even-better-read-unaligned branch from 7ed426a to fd33c1fCompareJuly 2, 2026 05:30
@rustbot

Copy link
Copy Markdown
Collaborator

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

@scottmcm
scottmcmforce-pushed the even-better-read-unaligned branch from fd33c1f to a576ef9CompareJuly 2, 2026 05:35
Comment on lines -42 to +41
StorageLive(_4);
_4 = copy (*_3);
_5 = copy _4 as T (Transmute);
StorageDead(_4);
_4 = copy ((*_3).0: T);

@scottmcmscottmcmJul 2, 2026

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The library change to use packed landed in #158427, so now this shows the critical change from this optimization...

View changes since the review

Comment on lines -25 to +26
// CHECK-NOT: !noundef
// CHECK-NOT: !range
// CHECK-SAME: !range [[R16:![0-9]+]]
// CHECK-SAME: !noundef

@scottmcmscottmcmJul 2, 2026

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

...which then means these loads get metadata on them without codegen changes.

View changes since the review

@scottmcm

Copy link
Copy Markdown
MemberAuthor

The more I poked at this the less I'm confident that SRoA is the correct answer here, especially since I tried going a bit further and ended up just getting things like this

 bb0: {
StorageLive(_3);
_3 = PtrMetadata(copy _1);
StorageLive(_5);
StorageLive(_4);
_4 = &raw const (*_1);
- _5 = copy _4 as std::ptr::NonNull<[T]> (Transmute);+ _5 = copy _4 as (*const [T]) is !null (Transmute);
StorageDead(_4);
StorageLive(_7);
StorageLive(_6);
_6 = copy _5 as *mut [T] (Transmute);
_7 = copy _6 as *mut T (PtrToPtr);
StorageDead(_6);
- _8 = copy _7 as std::ptr::NonNull<T> (Transmute);+ _8 = copy _7 as (*const T) is !null (Transmute);
StorageDead(_7);
StorageDead(_5);
switchInt(const <T as std::mem::SizedTypeProperties>::IS_ZST) -> [0: bb1, otherwise: bb2];
}

which is kinda the opposite of the direction in #153085 which I think would be nicer to see when reading the MIR.

@scottmcm
scottmcm marked this pull request as draft July 3, 2026 11:18
@rustbotrustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jul 3, 2026
@scottmcm

Copy link
Copy Markdown
MemberAuthor

Closing this in favour of fixing the motivating example in layout instead, #159033

@scottmcmscottmcm closed this Jul 9, 2026
@rustbotrustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Jul 9, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-mir-optArea: MIR optimizationsT-compilerRelevant 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.

3 participants

@scottmcm@rustbot@saethlin
, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' [mir-opt] Allow SRoA when an object is transmuted to a field type by scottmcm · Pull Request #158291 · rust-lang/rust · GitHub
Skip to content

[mir-opt] Allow SRoA when an object is transmuted to a field type - #158291

Closed
scottmcm wants to merge 1 commit into
rust-lang:mainfrom
scottmcm:even-better-read-unaligned
Closed

[mir-opt] Allow SRoA when an object is transmuted to a field type#158291
scottmcm wants to merge 1 commit into
rust-lang:mainfrom
scottmcm:even-better-read-unaligned

Conversation

@scottmcm

@scottmcmscottmcm commented Jun 23, 2026

Copy link
Copy Markdown
Member

Inspired by #158202 (comment), this allows SRoA to expand a local consumed by a CastKind::Transmute if that transmute is to the type of a field, since if it's to the type of a field we can just have it take the local for that field like we would if it was a field projection.

Future PRs could do more complex stuff, like using layout to always allow SRoA of x in Transmute(x) when x is https://doc.rust-lang.org/nightly/nightly-rustc/rustc_middle/ty/layout/type.TyAndLayout.html#method.non_1zst_field, but this is enough for the specific case I needed.

r? mir-opt

@rustbot

Copy link
Copy Markdown
Collaborator

Some changes occurred to MIR optimizations

cc @rust-lang/wg-mir-opt

@rustbotrustbot added 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. labels Jun 23, 2026
@scottmcmscottmcm added the A-mir-opt Area: MIR optimizations label Jun 24, 2026
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Jul 1, 2026
…d, r=aapoalas
Implement `ptr::{read,write}_unaligned` via `repr(packed)`
We already support doing unaligned reads & writes via `repr(packed)` fields, so this just uses that support from the backend rather than needing to thinks about `memcpy` and `intrinsics::forget` and such.
Turns out in codegen this ends up essentially identical because the packed type read gets `BackendRepr::Memory` and thus the read/write of the packed type *is* an `align 1` memcpy, just like the library code before this PR. But doing this gives much simpler MIR and rust-lang#158291 will make it better than the previous version by not needing to emit the `memcpy` at all for things like `read_unaligned::<u32>`.
First commit are some tests that pass on master; Second commit changes the implementation and shows the corresponding test changes.
r? libs
jhpratt added a commit to jhpratt/rust that referenced this pull request Jul 1, 2026
…d, r=aapoalas
Implement `ptr::{read,write}_unaligned` via `repr(packed)`
We already support doing unaligned reads & writes via `repr(packed)` fields, so this just uses that support from the backend rather than needing to thinks about `memcpy` and `intrinsics::forget` and such.
Turns out in codegen this ends up essentially identical because the packed type read gets `BackendRepr::Memory` and thus the read/write of the packed type *is* an `align 1` memcpy, just like the library code before this PR. But doing this gives much simpler MIR and rust-lang#158291 will make it better than the previous version by not needing to emit the `memcpy` at all for things like `read_unaligned::<u32>`.
First commit are some tests that pass on master; Second commit changes the implementation and shows the corresponding test changes.
r? libs
@scottmcm
scottmcmforce-pushed the even-better-read-unaligned branch from 7ed426a to fd33c1fCompareJuly 2, 2026 05:30
@rustbot

Copy link
Copy Markdown
Collaborator

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

@scottmcm
scottmcmforce-pushed the even-better-read-unaligned branch from fd33c1f to a576ef9CompareJuly 2, 2026 05:35
Comment on lines -42 to +41
StorageLive(_4);
_4 = copy (*_3);
_5 = copy _4 as T (Transmute);
StorageDead(_4);
_4 = copy ((*_3).0: T);

@scottmcmscottmcmJul 2, 2026

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The library change to use packed landed in #158427, so now this shows the critical change from this optimization...

View changes since the review

Comment on lines -25 to +26
// CHECK-NOT: !noundef
// CHECK-NOT: !range
// CHECK-SAME: !range [[R16:![0-9]+]]
// CHECK-SAME: !noundef

@scottmcmscottmcmJul 2, 2026

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

...which then means these loads get metadata on them without codegen changes.

View changes since the review

@scottmcm

Copy link
Copy Markdown
MemberAuthor

The more I poked at this the less I'm confident that SRoA is the correct answer here, especially since I tried going a bit further and ended up just getting things like this

 bb0: {
StorageLive(_3);
_3 = PtrMetadata(copy _1);
StorageLive(_5);
StorageLive(_4);
_4 = &raw const (*_1);
- _5 = copy _4 as std::ptr::NonNull<[T]> (Transmute);+ _5 = copy _4 as (*const [T]) is !null (Transmute);
StorageDead(_4);
StorageLive(_7);
StorageLive(_6);
_6 = copy _5 as *mut [T] (Transmute);
_7 = copy _6 as *mut T (PtrToPtr);
StorageDead(_6);
- _8 = copy _7 as std::ptr::NonNull<T> (Transmute);+ _8 = copy _7 as (*const T) is !null (Transmute);
StorageDead(_7);
StorageDead(_5);
switchInt(const <T as std::mem::SizedTypeProperties>::IS_ZST) -> [0: bb1, otherwise: bb2];
}

which is kinda the opposite of the direction in #153085 which I think would be nicer to see when reading the MIR.

@scottmcm
scottmcm marked this pull request as draft July 3, 2026 11:18
@rustbotrustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jul 3, 2026
@scottmcm

Copy link
Copy Markdown
MemberAuthor

Closing this in favour of fixing the motivating example in layout instead, #159033

@scottmcmscottmcm closed this Jul 9, 2026
@rustbotrustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Jul 9, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-mir-optArea: MIR optimizationsT-compilerRelevant 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.

3 participants

@scottmcm@rustbot@saethlin
, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + ' [mir-opt] Allow SRoA when an object is transmuted to a field type by scottmcm · Pull Request #158291 · rust-lang/rust · GitHub
Skip to content

[mir-opt] Allow SRoA when an object is transmuted to a field type - #158291

Closed
scottmcm wants to merge 1 commit into
rust-lang:mainfrom
scottmcm:even-better-read-unaligned
Closed

[mir-opt] Allow SRoA when an object is transmuted to a field type#158291
scottmcm wants to merge 1 commit into
rust-lang:mainfrom
scottmcm:even-better-read-unaligned

Conversation

@scottmcm

@scottmcmscottmcm commented Jun 23, 2026

Copy link
Copy Markdown
Member

Inspired by #158202 (comment), this allows SRoA to expand a local consumed by a CastKind::Transmute if that transmute is to the type of a field, since if it's to the type of a field we can just have it take the local for that field like we would if it was a field projection.

Future PRs could do more complex stuff, like using layout to always allow SRoA of x in Transmute(x) when x is https://doc.rust-lang.org/nightly/nightly-rustc/rustc_middle/ty/layout/type.TyAndLayout.html#method.non_1zst_field, but this is enough for the specific case I needed.

r? mir-opt

@rustbot

Copy link
Copy Markdown
Collaborator

Some changes occurred to MIR optimizations

cc @rust-lang/wg-mir-opt

@rustbotrustbot added 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. labels Jun 23, 2026
@scottmcmscottmcm added the A-mir-opt Area: MIR optimizations label Jun 24, 2026
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Jul 1, 2026
…d, r=aapoalas
Implement `ptr::{read,write}_unaligned` via `repr(packed)`
We already support doing unaligned reads & writes via `repr(packed)` fields, so this just uses that support from the backend rather than needing to thinks about `memcpy` and `intrinsics::forget` and such.
Turns out in codegen this ends up essentially identical because the packed type read gets `BackendRepr::Memory` and thus the read/write of the packed type *is* an `align 1` memcpy, just like the library code before this PR. But doing this gives much simpler MIR and rust-lang#158291 will make it better than the previous version by not needing to emit the `memcpy` at all for things like `read_unaligned::<u32>`.
First commit are some tests that pass on master; Second commit changes the implementation and shows the corresponding test changes.
r? libs
jhpratt added a commit to jhpratt/rust that referenced this pull request Jul 1, 2026
…d, r=aapoalas
Implement `ptr::{read,write}_unaligned` via `repr(packed)`
We already support doing unaligned reads & writes via `repr(packed)` fields, so this just uses that support from the backend rather than needing to thinks about `memcpy` and `intrinsics::forget` and such.
Turns out in codegen this ends up essentially identical because the packed type read gets `BackendRepr::Memory` and thus the read/write of the packed type *is* an `align 1` memcpy, just like the library code before this PR. But doing this gives much simpler MIR and rust-lang#158291 will make it better than the previous version by not needing to emit the `memcpy` at all for things like `read_unaligned::<u32>`.
First commit are some tests that pass on master; Second commit changes the implementation and shows the corresponding test changes.
r? libs
@scottmcm
scottmcmforce-pushed the even-better-read-unaligned branch from 7ed426a to fd33c1fCompareJuly 2, 2026 05:30
@rustbot

Copy link
Copy Markdown
Collaborator

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

@scottmcm
scottmcmforce-pushed the even-better-read-unaligned branch from fd33c1f to a576ef9CompareJuly 2, 2026 05:35
Comment on lines -42 to +41
StorageLive(_4);
_4 = copy (*_3);
_5 = copy _4 as T (Transmute);
StorageDead(_4);
_4 = copy ((*_3).0: T);

@scottmcmscottmcmJul 2, 2026

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The library change to use packed landed in #158427, so now this shows the critical change from this optimization...

View changes since the review

Comment on lines -25 to +26
// CHECK-NOT: !noundef
// CHECK-NOT: !range
// CHECK-SAME: !range [[R16:![0-9]+]]
// CHECK-SAME: !noundef

@scottmcmscottmcmJul 2, 2026

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

...which then means these loads get metadata on them without codegen changes.

View changes since the review

@scottmcm

Copy link
Copy Markdown
MemberAuthor

The more I poked at this the less I'm confident that SRoA is the correct answer here, especially since I tried going a bit further and ended up just getting things like this

 bb0: {
StorageLive(_3);
_3 = PtrMetadata(copy _1);
StorageLive(_5);
StorageLive(_4);
_4 = &raw const (*_1);
- _5 = copy _4 as std::ptr::NonNull<[T]> (Transmute);+ _5 = copy _4 as (*const [T]) is !null (Transmute);
StorageDead(_4);
StorageLive(_7);
StorageLive(_6);
_6 = copy _5 as *mut [T] (Transmute);
_7 = copy _6 as *mut T (PtrToPtr);
StorageDead(_6);
- _8 = copy _7 as std::ptr::NonNull<T> (Transmute);+ _8 = copy _7 as (*const T) is !null (Transmute);
StorageDead(_7);
StorageDead(_5);
switchInt(const <T as std::mem::SizedTypeProperties>::IS_ZST) -> [0: bb1, otherwise: bb2];
}

which is kinda the opposite of the direction in #153085 which I think would be nicer to see when reading the MIR.

@scottmcm
scottmcm marked this pull request as draft July 3, 2026 11:18
@rustbotrustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jul 3, 2026
@scottmcm

Copy link
Copy Markdown
MemberAuthor

Closing this in favour of fixing the motivating example in layout instead, #159033

@scottmcmscottmcm closed this Jul 9, 2026
@rustbotrustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Jul 9, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-mir-optArea: MIR optimizationsT-compilerRelevant 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.

3 participants

@scottmcm@rustbot@saethlin
, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' [mir-opt] Allow SRoA when an object is transmuted to a field type by scottmcm · Pull Request #158291 · rust-lang/rust · GitHub
Skip to content

[mir-opt] Allow SRoA when an object is transmuted to a field type - #158291

Closed
scottmcm wants to merge 1 commit into
rust-lang:mainfrom
scottmcm:even-better-read-unaligned
Closed

[mir-opt] Allow SRoA when an object is transmuted to a field type#158291
scottmcm wants to merge 1 commit into
rust-lang:mainfrom
scottmcm:even-better-read-unaligned

Conversation

@scottmcm

@scottmcmscottmcm commented Jun 23, 2026

Copy link
Copy Markdown
Member

Inspired by #158202 (comment), this allows SRoA to expand a local consumed by a CastKind::Transmute if that transmute is to the type of a field, since if it's to the type of a field we can just have it take the local for that field like we would if it was a field projection.

Future PRs could do more complex stuff, like using layout to always allow SRoA of x in Transmute(x) when x is https://doc.rust-lang.org/nightly/nightly-rustc/rustc_middle/ty/layout/type.TyAndLayout.html#method.non_1zst_field, but this is enough for the specific case I needed.

r? mir-opt

@rustbot

Copy link
Copy Markdown
Collaborator

Some changes occurred to MIR optimizations

cc @rust-lang/wg-mir-opt

@rustbotrustbot added 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. labels Jun 23, 2026
@scottmcmscottmcm added the A-mir-opt Area: MIR optimizations label Jun 24, 2026
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Jul 1, 2026
…d, r=aapoalas
Implement `ptr::{read,write}_unaligned` via `repr(packed)`
We already support doing unaligned reads & writes via `repr(packed)` fields, so this just uses that support from the backend rather than needing to thinks about `memcpy` and `intrinsics::forget` and such.
Turns out in codegen this ends up essentially identical because the packed type read gets `BackendRepr::Memory` and thus the read/write of the packed type *is* an `align 1` memcpy, just like the library code before this PR. But doing this gives much simpler MIR and rust-lang#158291 will make it better than the previous version by not needing to emit the `memcpy` at all for things like `read_unaligned::<u32>`.
First commit are some tests that pass on master; Second commit changes the implementation and shows the corresponding test changes.
r? libs
jhpratt added a commit to jhpratt/rust that referenced this pull request Jul 1, 2026
…d, r=aapoalas
Implement `ptr::{read,write}_unaligned` via `repr(packed)`
We already support doing unaligned reads & writes via `repr(packed)` fields, so this just uses that support from the backend rather than needing to thinks about `memcpy` and `intrinsics::forget` and such.
Turns out in codegen this ends up essentially identical because the packed type read gets `BackendRepr::Memory` and thus the read/write of the packed type *is* an `align 1` memcpy, just like the library code before this PR. But doing this gives much simpler MIR and rust-lang#158291 will make it better than the previous version by not needing to emit the `memcpy` at all for things like `read_unaligned::<u32>`.
First commit are some tests that pass on master; Second commit changes the implementation and shows the corresponding test changes.
r? libs
@scottmcm
scottmcmforce-pushed the even-better-read-unaligned branch from 7ed426a to fd33c1fCompareJuly 2, 2026 05:30
@rustbot

Copy link
Copy Markdown
Collaborator

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

@scottmcm
scottmcmforce-pushed the even-better-read-unaligned branch from fd33c1f to a576ef9CompareJuly 2, 2026 05:35
Comment on lines -42 to +41
StorageLive(_4);
_4 = copy (*_3);
_5 = copy _4 as T (Transmute);
StorageDead(_4);
_4 = copy ((*_3).0: T);

@scottmcmscottmcmJul 2, 2026

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The library change to use packed landed in #158427, so now this shows the critical change from this optimization...

View changes since the review

Comment on lines -25 to +26
// CHECK-NOT: !noundef
// CHECK-NOT: !range
// CHECK-SAME: !range [[R16:![0-9]+]]
// CHECK-SAME: !noundef

@scottmcmscottmcmJul 2, 2026

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

...which then means these loads get metadata on them without codegen changes.

View changes since the review

@scottmcm

Copy link
Copy Markdown
MemberAuthor

The more I poked at this the less I'm confident that SRoA is the correct answer here, especially since I tried going a bit further and ended up just getting things like this

 bb0: {
StorageLive(_3);
_3 = PtrMetadata(copy _1);
StorageLive(_5);
StorageLive(_4);
_4 = &raw const (*_1);
- _5 = copy _4 as std::ptr::NonNull<[T]> (Transmute);+ _5 = copy _4 as (*const [T]) is !null (Transmute);
StorageDead(_4);
StorageLive(_7);
StorageLive(_6);
_6 = copy _5 as *mut [T] (Transmute);
_7 = copy _6 as *mut T (PtrToPtr);
StorageDead(_6);
- _8 = copy _7 as std::ptr::NonNull<T> (Transmute);+ _8 = copy _7 as (*const T) is !null (Transmute);
StorageDead(_7);
StorageDead(_5);
switchInt(const <T as std::mem::SizedTypeProperties>::IS_ZST) -> [0: bb1, otherwise: bb2];
}

which is kinda the opposite of the direction in #153085 which I think would be nicer to see when reading the MIR.

@scottmcm
scottmcm marked this pull request as draft July 3, 2026 11:18
@rustbotrustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jul 3, 2026
@scottmcm

Copy link
Copy Markdown
MemberAuthor

Closing this in favour of fixing the motivating example in layout instead, #159033

@scottmcmscottmcm closed this Jul 9, 2026
@rustbotrustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Jul 9, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-mir-optArea: MIR optimizationsT-compilerRelevant 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.

3 participants

@scottmcm@rustbot@saethlin
, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' [mir-opt] Allow SRoA when an object is transmuted to a field type by scottmcm · Pull Request #158291 · rust-lang/rust · GitHub
Skip to content

[mir-opt] Allow SRoA when an object is transmuted to a field type - #158291

Closed
scottmcm wants to merge 1 commit into
rust-lang:mainfrom
scottmcm:even-better-read-unaligned
Closed

[mir-opt] Allow SRoA when an object is transmuted to a field type#158291
scottmcm wants to merge 1 commit into
rust-lang:mainfrom
scottmcm:even-better-read-unaligned

Conversation

@scottmcm

@scottmcmscottmcm commented Jun 23, 2026

Copy link
Copy Markdown
Member

Inspired by #158202 (comment), this allows SRoA to expand a local consumed by a CastKind::Transmute if that transmute is to the type of a field, since if it's to the type of a field we can just have it take the local for that field like we would if it was a field projection.

Future PRs could do more complex stuff, like using layout to always allow SRoA of x in Transmute(x) when x is https://doc.rust-lang.org/nightly/nightly-rustc/rustc_middle/ty/layout/type.TyAndLayout.html#method.non_1zst_field, but this is enough for the specific case I needed.

r? mir-opt

@rustbot

Copy link
Copy Markdown
Collaborator

Some changes occurred to MIR optimizations

cc @rust-lang/wg-mir-opt

@rustbotrustbot added 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. labels Jun 23, 2026
@scottmcmscottmcm added the A-mir-opt Area: MIR optimizations label Jun 24, 2026
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Jul 1, 2026
…d, r=aapoalas
Implement `ptr::{read,write}_unaligned` via `repr(packed)`
We already support doing unaligned reads & writes via `repr(packed)` fields, so this just uses that support from the backend rather than needing to thinks about `memcpy` and `intrinsics::forget` and such.
Turns out in codegen this ends up essentially identical because the packed type read gets `BackendRepr::Memory` and thus the read/write of the packed type *is* an `align 1` memcpy, just like the library code before this PR. But doing this gives much simpler MIR and rust-lang#158291 will make it better than the previous version by not needing to emit the `memcpy` at all for things like `read_unaligned::<u32>`.
First commit are some tests that pass on master; Second commit changes the implementation and shows the corresponding test changes.
r? libs
jhpratt added a commit to jhpratt/rust that referenced this pull request Jul 1, 2026
…d, r=aapoalas
Implement `ptr::{read,write}_unaligned` via `repr(packed)`
We already support doing unaligned reads & writes via `repr(packed)` fields, so this just uses that support from the backend rather than needing to thinks about `memcpy` and `intrinsics::forget` and such.
Turns out in codegen this ends up essentially identical because the packed type read gets `BackendRepr::Memory` and thus the read/write of the packed type *is* an `align 1` memcpy, just like the library code before this PR. But doing this gives much simpler MIR and rust-lang#158291 will make it better than the previous version by not needing to emit the `memcpy` at all for things like `read_unaligned::<u32>`.
First commit are some tests that pass on master; Second commit changes the implementation and shows the corresponding test changes.
r? libs
@scottmcm
scottmcmforce-pushed the even-better-read-unaligned branch from 7ed426a to fd33c1fCompareJuly 2, 2026 05:30
@rustbot

Copy link
Copy Markdown
Collaborator

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

@scottmcm
scottmcmforce-pushed the even-better-read-unaligned branch from fd33c1f to a576ef9CompareJuly 2, 2026 05:35
Comment on lines -42 to +41
StorageLive(_4);
_4 = copy (*_3);
_5 = copy _4 as T (Transmute);
StorageDead(_4);
_4 = copy ((*_3).0: T);

@scottmcmscottmcmJul 2, 2026

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The library change to use packed landed in #158427, so now this shows the critical change from this optimization...

View changes since the review

Comment on lines -25 to +26
// CHECK-NOT: !noundef
// CHECK-NOT: !range
// CHECK-SAME: !range [[R16:![0-9]+]]
// CHECK-SAME: !noundef

@scottmcmscottmcmJul 2, 2026

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

...which then means these loads get metadata on them without codegen changes.

View changes since the review

@scottmcm

Copy link
Copy Markdown
MemberAuthor

The more I poked at this the less I'm confident that SRoA is the correct answer here, especially since I tried going a bit further and ended up just getting things like this

 bb0: {
StorageLive(_3);
_3 = PtrMetadata(copy _1);
StorageLive(_5);
StorageLive(_4);
_4 = &raw const (*_1);
- _5 = copy _4 as std::ptr::NonNull<[T]> (Transmute);+ _5 = copy _4 as (*const [T]) is !null (Transmute);
StorageDead(_4);
StorageLive(_7);
StorageLive(_6);
_6 = copy _5 as *mut [T] (Transmute);
_7 = copy _6 as *mut T (PtrToPtr);
StorageDead(_6);
- _8 = copy _7 as std::ptr::NonNull<T> (Transmute);+ _8 = copy _7 as (*const T) is !null (Transmute);
StorageDead(_7);
StorageDead(_5);
switchInt(const <T as std::mem::SizedTypeProperties>::IS_ZST) -> [0: bb1, otherwise: bb2];
}

which is kinda the opposite of the direction in #153085 which I think would be nicer to see when reading the MIR.

@scottmcm
scottmcm marked this pull request as draft July 3, 2026 11:18
@rustbotrustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jul 3, 2026
@scottmcm

Copy link
Copy Markdown
MemberAuthor

Closing this in favour of fixing the motivating example in layout instead, #159033

@scottmcmscottmcm closed this Jul 9, 2026
@rustbotrustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Jul 9, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-mir-optArea: MIR optimizationsT-compilerRelevant 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.

3 participants

@scottmcm@rustbot@saethlin
, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })(); [mir-opt] Allow SRoA when an object is transmuted to a field type by scottmcm · Pull Request #158291 · rust-lang/rust · GitHub
Skip to content

[mir-opt] Allow SRoA when an object is transmuted to a field type - #158291

Closed
scottmcm wants to merge 1 commit into
rust-lang:mainfrom
scottmcm:even-better-read-unaligned
Closed

[mir-opt] Allow SRoA when an object is transmuted to a field type#158291
scottmcm wants to merge 1 commit into
rust-lang:mainfrom
scottmcm:even-better-read-unaligned

Conversation

@scottmcm

@scottmcmscottmcm commented Jun 23, 2026

Copy link
Copy Markdown
Member

Inspired by #158202 (comment), this allows SRoA to expand a local consumed by a CastKind::Transmute if that transmute is to the type of a field, since if it's to the type of a field we can just have it take the local for that field like we would if it was a field projection.

Future PRs could do more complex stuff, like using layout to always allow SRoA of x in Transmute(x) when x is https://doc.rust-lang.org/nightly/nightly-rustc/rustc_middle/ty/layout/type.TyAndLayout.html#method.non_1zst_field, but this is enough for the specific case I needed.

r? mir-opt

@rustbot

Copy link
Copy Markdown
Collaborator

Some changes occurred to MIR optimizations

cc @rust-lang/wg-mir-opt

@rustbotrustbot added 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. labels Jun 23, 2026
@scottmcmscottmcm added the A-mir-opt Area: MIR optimizations label Jun 24, 2026
JonathanBrouwer added a commit to JonathanBrouwer/rust that referenced this pull request Jul 1, 2026
…d, r=aapoalas
Implement `ptr::{read,write}_unaligned` via `repr(packed)`
We already support doing unaligned reads & writes via `repr(packed)` fields, so this just uses that support from the backend rather than needing to thinks about `memcpy` and `intrinsics::forget` and such.
Turns out in codegen this ends up essentially identical because the packed type read gets `BackendRepr::Memory` and thus the read/write of the packed type *is* an `align 1` memcpy, just like the library code before this PR. But doing this gives much simpler MIR and rust-lang#158291 will make it better than the previous version by not needing to emit the `memcpy` at all for things like `read_unaligned::<u32>`.
First commit are some tests that pass on master; Second commit changes the implementation and shows the corresponding test changes.
r? libs
jhpratt added a commit to jhpratt/rust that referenced this pull request Jul 1, 2026
…d, r=aapoalas
Implement `ptr::{read,write}_unaligned` via `repr(packed)`
We already support doing unaligned reads & writes via `repr(packed)` fields, so this just uses that support from the backend rather than needing to thinks about `memcpy` and `intrinsics::forget` and such.
Turns out in codegen this ends up essentially identical because the packed type read gets `BackendRepr::Memory` and thus the read/write of the packed type *is* an `align 1` memcpy, just like the library code before this PR. But doing this gives much simpler MIR and rust-lang#158291 will make it better than the previous version by not needing to emit the `memcpy` at all for things like `read_unaligned::<u32>`.
First commit are some tests that pass on master; Second commit changes the implementation and shows the corresponding test changes.
r? libs
@scottmcm
scottmcmforce-pushed the even-better-read-unaligned branch from 7ed426a to fd33c1fCompareJuly 2, 2026 05:30
@rustbot

Copy link
Copy Markdown
Collaborator

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

@scottmcm
scottmcmforce-pushed the even-better-read-unaligned branch from fd33c1f to a576ef9CompareJuly 2, 2026 05:35
Comment on lines -42 to +41
StorageLive(_4);
_4 = copy (*_3);
_5 = copy _4 as T (Transmute);
StorageDead(_4);
_4 = copy ((*_3).0: T);

@scottmcmscottmcmJul 2, 2026

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The library change to use packed landed in #158427, so now this shows the critical change from this optimization...

View changes since the review

Comment on lines -25 to +26
// CHECK-NOT: !noundef
// CHECK-NOT: !range
// CHECK-SAME: !range [[R16:![0-9]+]]
// CHECK-SAME: !noundef

@scottmcmscottmcmJul 2, 2026

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

...which then means these loads get metadata on them without codegen changes.

View changes since the review

@scottmcm

Copy link
Copy Markdown
MemberAuthor

The more I poked at this the less I'm confident that SRoA is the correct answer here, especially since I tried going a bit further and ended up just getting things like this

 bb0: {
StorageLive(_3);
_3 = PtrMetadata(copy _1);
StorageLive(_5);
StorageLive(_4);
_4 = &raw const (*_1);
- _5 = copy _4 as std::ptr::NonNull<[T]> (Transmute);+ _5 = copy _4 as (*const [T]) is !null (Transmute);
StorageDead(_4);
StorageLive(_7);
StorageLive(_6);
_6 = copy _5 as *mut [T] (Transmute);
_7 = copy _6 as *mut T (PtrToPtr);
StorageDead(_6);
- _8 = copy _7 as std::ptr::NonNull<T> (Transmute);+ _8 = copy _7 as (*const T) is !null (Transmute);
StorageDead(_7);
StorageDead(_5);
switchInt(const <T as std::mem::SizedTypeProperties>::IS_ZST) -> [0: bb1, otherwise: bb2];
}

which is kinda the opposite of the direction in #153085 which I think would be nicer to see when reading the MIR.

@scottmcm
scottmcm marked this pull request as draft July 3, 2026 11:18
@rustbotrustbot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jul 3, 2026
@scottmcm

Copy link
Copy Markdown
MemberAuthor

Closing this in favour of fixing the motivating example in layout instead, #159033

@scottmcmscottmcm closed this Jul 9, 2026
@rustbotrustbot removed the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Jul 9, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-mir-optArea: MIR optimizationsT-compilerRelevant 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.

3 participants

@scottmcm@rustbot@saethlin