Introduce -Z pack-coroutine-layout flag - #159795
Conversation
|
Some changes occurred to MIR optimizations cc @rust-lang/wg-mir-opt These commits modify the If this was unintentional then you should revert the changes before this PR is merged. |
This comment has been minimized.
This comment has been minimized.
5ab688f to
ce492c5
Compare
This comment has been minimized.
This comment has been minimized.
|
The second commit is not what I'd describe as cosmetic. It contains quite a lot of behaviour changes that should stay in the main PR. |
This comment has been minimized.
This comment has been minimized.
ce492c5 to
f850e99
Compare
|
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. |
|
Sorry for the late reply. I wasn't completely splitting this commit in a proper way. This time it should stay very cosmetic. |
-Z coroutine-layout flag-Z pack-coroutine-layout flag
We will now give users two options, to go with the traditional coroutine layout as of Dec 2025 or the new proposed compact layout. The compact layout will be documented in the RelocateUpvar MIR pass later. Co-authored-by: Dario Nieuwenhuis <dirbaio@dirbaio.net> Signed-off-by: Xiangfei Ding <dingxiangfei2009@protonmail.ch>
f850e99 to
81b4856
Compare
|
The job Click to see the possible cause of the failure (guessed by this bot) |
This is still mostly cosmetic, but more stuff is coming over from #135527.
Only the tip of the branch matters, the other commit will be shipped from another PR. It will go away after a rebase, hopefully.
r? @cjgillot