================
@@ -35,26 +33,29 @@ struct CDerived : NSP_1::CLeft, NSP_2::CRight {
int fooDerived() { return 3; };
};
+void use(void *, ...);
+
int main() {
NSP::CBase Base;
NSP_1::CLeft Left;
NSP_2::CRight Right;
CDerived Derived;
+ use(&Base, &Left, &Right, &Derived);
return 0;
}
-// RUN: %clang --target=x86_64-linux -Xclang -disable-O0-optnone -Xclang
-disable-llvm-passes -emit-llvm -S -g %s -o - | FileCheck %s
+// RUN: %clang_cc1 -triple x86_64-linux -emit-llvm -debug-info-kind=limited
-dwarf-version=5 -O1 %s -o - | FileCheck %s
----------------
jmorse wrote:
Is the use of `-O1` needed here? Ideally we would only test clang behaviours in
the clang tests, without making use of LLVM transformations as well. If it's
necessary to cover optimisation behaviours, we might need specific tests in the
llvm/test directory. (Similar with a few RUN lines below).
(This is a neatness objective rather than something specifically technical).
https://github.com/llvm/llvm-project/pull/151818
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
