================
@@ -0,0 +1,414 @@
+// Actual triple does not matter, just ensuring that the ABI being used for
+// mangling and similar is consistent. Choosing x86_64 as that seems to be a
+// configured target for most build configurations
+// RUN: %clang_cc1 -triple=x86_64 -std=c++26 %s -emit-llvm -O3
-o - | FileCheck %s
+// RUN: %clang_cc1 -triple=x86_64 -std=c++26 %s -emit-llvm -O3
-fstrict-vtable-pointers -o - | FileCheck %s --check-prefix=STRICT
----------------
ChuanqiXu9 wrote:
Yeah.
nitpicking: not "correct" but "expected". (Although this doesn't matter). The
idea is, actually we only changes/controls the CodeGen part. But we need the
middle end part to optimize it. Then the new added test is helpful if someday
the test fails, we can get the problem quickly to see if it is due to the
CodeGen or due to the middle end part.
https://github.com/llvm/llvm-project/pull/165341
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
