update bpf abi to match Clang 23 - #161076
Conversation
This comment has been minimized.
This comment has been minimized.
1cba5c3 to
8de7f71
Compare
|
r? @jieyouxu rustbot has assigned @jieyouxu. Use Why was this reviewer chosen?The reviewer was selected based on:
|
|
I checked the C ABI path with extern "C" using the same aggregate cases as the Clang change Since the new tests here are using the Rust ABI would it make sense to add a small extern "C" regression test too? |
|
Thanks for taking a look!
Whoops, should have done this while more awake. In practice they are the same so that is why the CHECKs work but given that this tests ABI the tests should use |
8de7f71 to
74adfe0
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. |
74adfe0 to
ed1978b
Compare
ed1978b to
be32f36
Compare
| // CHECK-LABEL: define{{.*}} i8 @bar0( | ||
| // CHECK: ret i8 | ||
| #[no_mangle] | ||
| extern "C" fn bar0(a: i8) -> Foo0 { | ||
| Foo0 { a } | ||
| } |
There was a problem hiding this comment.
for BE this is a bit surprising to me, in many targets this would instead pass an i32 or i64 on BE so that the 8 actual bits are in the right spot. But, this is consistent with clang
There was a problem hiding this comment.
Looks good to me, but I would like to make sure that this doesn't break any integration tests of https://github.com/aya-rs/aya. I will come back with an answer at the start of coming week.
mirror the behavior of llvm/llvm-project#206876
apparently we have no target maintainers for the bpf targets... fun.