-
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
[WIP] rustc_mir: use FnAbi to get abi::call::Conv in miri. #66807
Conversation
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
☔ The latest upstream changes (presumably #66950) made this pull request unmergeable. Please resolve the merge conflicts. |
Ping from triage |
I have no plans to finish this right now, if anything changes I'll reopen later. |
Based on #65947.
I wanted to include this (i.e. only the last commit) in #65947, but I forgot that
rustc_target::abi::call
requires<Cx as LayoutOf>::TyLayout == TyLayout<Ty>
, which works well enough for codegen (which ICEs on layout errors, since there's nothing else to do), but not miri.I don't think this can land without a cleanup of the
rustc_target::abi
/rustc::ty::layout
code to bake inResult
(instead of doing all theMaybeResult
dances), and either a lot of.unwrap()
in codegen or maybe adding aget
method (via extension trait?) toResult<T, !>
.r? @oli-obk cc @RalfJung