D109607 results in a regression in llvm-test-suite.
The reason is we didn't check the size of SourceTy, so that we will
return wrong SSE type when SourceTy is overlapped.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
I'm wondering whether the test case is required or not for this patch. Reasons:
- We have a test in llvm-test-suite can cover this and the test is just a snippet of it;
- The test case can not reflect the direct effect of this change;
- There're many variables in IR which may be easily affected by unrelated changes, which is annoying to others.
What do you think?
clang/test/CodeGen/X86/va-arg-sse.c | ||
---|---|---|
2 | Please don't use -O* in clang irgen tests. |
The test-suite is an end-to-end/integration test while tests monorepository are unit/regression tests. They have different purposes.
(Personally, I would prefer to reduce the amount of unit/regression testing that can already be covered by the test-suite, but that would be a bigger story)
clang/test/CodeGen/X86/va-arg-sse.c | ||
---|---|---|
2 | I agree here, testing -O* output will break easily with any unrelated change in LLVM. |
clang/test/CodeGen/X86/va-arg-sse.c | ||
---|---|---|
2 | You are right. The test case looks more clear now. |
Please don't use -O* in clang irgen tests.
This should *only* test what IR is produced by clang itself.