================ @@ -0,0 +1,45 @@ +// RUN: %clang_cc1 -fsanitize=alloc-token -falloc-token-max=2147483647 -triple x86_64-linux-gnu -x c -emit-llvm %s -o - | FileCheck %s ---------------- zmodem wrote:
I can sympathize with wanting to test the end-to-end behavior, but maybe that could be put in a separate test, and use only one or two allocator variants? The point is mainly to check that the pass pipeline is set up right both for -O0 and higher, right? The current version of the patch, which combines -O0, -O, and -disable-llvm-passes with all the different allocators, and uses generated checks, makes it very hard to see what behavior it's actually testing for. https://github.com/llvm/llvm-project/pull/156839 _______________________________________________ llvm-branch-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
