c9bd88e681
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
18 lines
467 B
C++
18 lines
467 B
C++
// RUN: %clang_cc1 -triple %itanium_abi_triple -emit-llvm -o - %s | FileCheck %s
|
|
|
|
const int x = 10;
|
|
const int y = 20;
|
|
const volatile int z = 30;
|
|
// CHECK-NOT: @x
|
|
// CHECK: @z = constant i32 30
|
|
// CHECK: @_ZL1y = internal constant i32 20
|
|
const int& b() { return y; }
|
|
|
|
const char z1[] = "asdf";
|
|
const char z2[] = "zxcv";
|
|
const volatile char z3[] = "zxcv";
|
|
// CHECK-NOT: @z1
|
|
// CHECK: @z3 = constant
|
|
// CHECK: @_ZL2z2 = internal constant
|
|
const char* b2() { return z2; }
|