tests: codegen-llvm: Update bpf-alu32 with the new LLVM attributes#157249
tests: codegen-llvm: Update bpf-alu32 with the new LLVM attributes#157249vadorovsky wants to merge 3 commits into
Conversation
|
Failed to set assignee to
|
Done. Another thing - should I use |
|
It looks like the test was added in 9cf2170 and the purpose seems to basically just be "target features on bpf work". TBH I'm not sure this should be a codegen test at all (at least then it should probably actually check for the But yes, as this is not actually intending to test any ABI behavior on BPF, using |
|
Agreed, I'm pretty sure we can |
This comment has been minimized.
This comment has been minimized.
I would keep the codegen test, but I agree with adding a check for the That said, I also think it would be nice to have a separate UI test for the |
Not strictly opposed, but I'm not sure what additional value an UI test would add over the codegen test? |
The LLVM backend now emits `noundef zeroext` on `i8` return values and `noundef` on `i8` parameters. Update the FileCheck pattern to match those, and any possible future attributes.
Instead of keeping it as `only-bpf`, use minicore. This way we make sure it will never get outdated again.
Check whether the `"target-feature"` attribure was actually emitted in LLVM IR.
c249a60 to
06edf3d
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. |
Probably none. I adjusted the codegen test instead, PTAL. |
The LLVM backend now emits
noundef zeroextoni8return values andnoundefoni8parameters. Update the FileCheck pattern to match.r? @nagisa