kpn added a comment. In D118259#3389246 <https://reviews.llvm.org/D118259#3389246>, @fhahn wrote:
> In D118259#3389235 <https://reviews.llvm.org/D118259#3389235>, @kpn wrote: > >> It's been a while, but I think the aarch64-neon-intrinsics-constrained.c >> test is trimmed down from the aarch64-neon-intrinsics.c test. Shouldn't the >> constrained and non-constrained end-to-end tests be treated the same? > > Are you referring to > https://github.com/llvm/llvm-project/blob/main/clang/test/CodeGen/aarch64-neon-intrinsics.c? > This one doesn't check assembly. Ah, well, I guess that wasn't it, then. It's been a while, and I've been all over the place. A clang-only test that just tests for the correct IR being emitted won't trigger the failures in the backend. An LLVM-only test that starts from that IR can show those failures, but it also runs the risk over time of getting out of sync with the IR emitted by clang. An end-to-end test will always be in sync, and it will show those failures that I ran into plus anything else that crops up over time. If there's another way, or if there is another approach, then it might be possible there's a way to get all the testing done without running into those issues. I just don't know what it is. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D118259/new/ https://reviews.llvm.org/D118259 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
