-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
rustc_target: separate out an individual alignment quantity type from Align. #54071
Conversation
☔ The latest upstream changes (presumably #53998) made this pull request unmergeable. Please resolve the merge conflicts. |
Triage; @eddyb This PR needs to be rebased. |
Ping from triage @eddyb: It looks like this PR is ready to be merged except for a rebase. |
Ping from triage @eddyb: We haven't heard from you in a while about this PR, so I'm closing this as per our triage guidelines. Thanks for your contribution and please feel free to re-open in the future. |
@bors r+ |
📌 Commit 5b4747d has been approved by |
⌛ Testing commit 5b4747d with merge d75e9c6a2e2f85498c4092d61ea763c813997bb6... |
@bors retry Yielding priority to the beta-accepted stuff. |
⌛ Testing commit 5b4747d with merge c72ccd655ce4979dd1551afe11aa4335c2e21298... |
@bors retry Yielding priority to the beta rollup. |
rustc_target: separate out an individual alignment quantity type from Align. Before this PR, `rustc_target::abi::Align` combined "power-of-two alignment quantity" semantics, with a distinction between ABI (required) and preferred alignment (by having two quantities). After this PR, `Align` is only *one* such quantity, and a new `AbiAndPrefAlign` type is introduced to hold the pair of ABI and preferred `Align` quantities. `Align` is used everywhere one quantity is necessary/sufficient, simplifying some of the code in codegen/miri, while `AbiAndPrefAlign` only in layout computation (to propagate preferred alignment). r? @oli-obk cc @nagisa @RalfJung @nikomatsakis
☀️ Test successful - status-appveyor, status-travis |
📣 Toolstate changed by #54071! Tested on commit 6a2d1b4. 💔 clippy-driver on windows: test-pass → build-fail (cc @Manishearth @llogiq @mcarton @oli-obk, @rust-lang/infra). |
Tested on commit rust-lang/rust@6a2d1b4. Direct link to PR: <rust-lang/rust#54071> 💔 clippy-driver on windows: test-pass → build-fail (cc @Manishearth @llogiq @mcarton @oli-obk, @rust-lang/infra). 💔 clippy-driver on linux: test-pass → build-fail (cc @Manishearth @llogiq @mcarton @oli-obk, @rust-lang/infra). 💔 rls on windows: test-fail → build-fail (cc @nrc @Xanewok, @rust-lang/infra). 💔 rls on linux: test-fail → build-fail (cc @nrc @Xanewok, @rust-lang/infra).
Changes: ```` rustup rust-lang#54071 dependencies: update pulldown-cmark from 0.1 to 0.2 s/file_map/source_map ````
@rustbot modify labels to -S-inactive-closed |
Changes: ```` rustup rust-lang/rust#54071 dependencies: update pulldown-cmark from 0.1 to 0.2 s/file_map/source_map ````
Before this PR,
rustc_target::abi::Align
combined "power-of-two alignment quantity" semantics, with a distinction between ABI (required) and preferred alignment (by having two quantities).After this PR,
Align
is only one such quantity, and a newAbiAndPrefAlign
type is introduced to hold the pair of ABI and preferredAlign
quantities.Align
is used everywhere one quantity is necessary/sufficient, simplifying some of the code in codegen/miri, whileAbiAndPrefAlign
only in layout computation (to propagate preferred alignment).r? @oli-obk cc @nagisa @RalfJung @nikomatsakis