llvm-project/clang/test/CodeGenCXX/PR5093-static-member-functi...

// RUN: %clang_cc1 %s -emit-llvm -triple %itanium_abi_triple -o - | FileCheck %s
struct a {
  static void f();
};

void g(a *a) {
  // CHECK: call {{.*}}void @_ZN1a1fEv()
  a->f();
}
Remove the -cxx-abi command-line flag. This makes the C++ ABI depend entirely on the target: MS ABI for -win32 triples, Itanium otherwise. It's no longer possible to do weird combinations. To be able to run a test with a specific ABI without constraining it to a specific triple, new substitutions are added to lit: %itanium_abi_triple and %ms_abi_triple can be used to get the current target triple adjusted to the desired ABI. For example, if the test suite is running with the i686-pc-win32 target, %itanium_abi_triple will expand to i686-pc-mingw32. Differential Revision: http://llvm-reviews.chandlerc.com/D2545 llvm-svn: 199250 2014-01-15 03:35:09 +08:00			`// RUN: %clang_cc1 %s -emit-llvm -triple %itanium_abi_triple -o - \| FileCheck %s`
Handle CXXMemberCallExprs that point to a static method. Fixes PR5093. llvm-svn: 83045 2009-09-29 11:54:11 +08:00			`struct a {`
			`static void f();`
			`};`

			`void g(a *a) {`
Account for calling convention specifiers in function definitions in IR test cases Several tests wouldn't pass when executed on an armv7a_pc_linux triple due to the non-default arm_aapcs calling convention produced on the function definitions in the IR output. Account for this with the application of a little regex. Patch by Ying Yi. llvm-svn: 240971 2015-06-30 01:29:50 +08:00			`// CHECK: call {{.*}}void @_ZN1a1fEv()`
Handle CXXMemberCallExprs that point to a static method. Fixes PR5093. llvm-svn: 83045 2009-09-29 11:54:11 +08:00			`a->f();`
			`}`