llvm-project/clang/test/CodeGenCXX/pr11797.cpp

// RUN: %clang_cc1 %s -fvisibility hidden -triple %itanium_abi_triple -emit-llvm -o - | FileCheck %s

namespace std __attribute__ ((__visibility__ ("default"))) {}
#pragma GCC visibility push(default)
void foo() {
}
#pragma GCC visibility pop
// CHECK-LABEL: define {{.*}}void @_Z3foov()
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 -fvisibility hidden -triple %itanium_abi_triple -emit-llvm -o - \| FileCheck %s`
Fix our handling of #pragma GCC visibility. Now the lexer just produces a token and the parser is the one responsible for activating it. This fixes problem like the one pr11797 where the lexer and the parser were not in sync. This also let us be more strict on where in the file we accept these pragmas. llvm-svn: 149014 2012-01-26 10:02:57 +08:00
			`namespace std __attribute__ ((__visibility__ ("default"))) {}`
			`#pragma GCC visibility push(default)`
			`void foo() {`
			`}`
			`#pragma GCC visibility pop`
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-LABEL: define {{.*}}void @_Z3foov()`