Don't compute FnAbi for LLVM intrinsics in backends#150768
Don't compute FnAbi for LLVM intrinsics in backends#150768bjorn3 wants to merge 3 commits intorust-lang:mainfrom
Conversation
|
These commits modify compiler targets. Some changes occurred in compiler/rustc_codegen_gcc |
|
r? @wesleywiser rustbot has assigned @wesleywiser. Use |
This comment has been minimized.
This comment has been minimized.
fb63e0c to
af005a9
Compare
This comment has been minimized.
This comment has been minimized.
e48fbd3 to
b05795a
Compare
This comment has been minimized.
This comment has been minimized.
b05795a to
83e77ec
Compare
This comment has been minimized.
This comment has been minimized.
83e77ec to
f1ab003
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. |
|
I've removed the removal of computing an |
| } | ||
| _ => unreachable!(), | ||
| }; | ||
| assert!(!fn_sig.c_variadic); |
There was a problem hiding this comment.
why this assertion? I mean I get the point that there are very few LLVM intrinsics that use vararg arguments, but I don't get what exactly fails for vararg functions
There was a problem hiding this comment.
Because varargs are not handled. For varargs the LLVM function signature must only contain the non-varargs + an indication that the function is a vararg. Given that afaik we don't currently use any LLVM intrinsics that use varargs, I didn't implement that.
This removes support forextern "unadjusted"for anything other than LLVM intrinsics. It only makes sense in the context of calling LLVM intrinsics anyway as it exposes the way the LLVM backend internally represents types. Perhaps it should be renamed toextern "llvm-intrinsic"?Follow up to #148533