e595e1ade0
Init-order and use-after-return modes can currently be enabled by runtime flags. use-after-scope mode is not really working at the moment. The only problem I see is that users won't be able to disable extra instrumentation for init-order and use-after-scope by a top-level Clang flag. But this instrumentation was implicitly enabled for quite a while and we didn't hear from users hurt by it. llvm-svn: 210924
28 lines
1.1 KiB
C++
28 lines
1.1 KiB
C++
// Constexpr:
|
|
// We need to check that a global variable initialized with a constexpr
|
|
// constructor can be accessed during dynamic initialization (as a constexpr
|
|
// constructor implies that it was initialized during constant initialization,
|
|
// not dynamic initialization).
|
|
|
|
// RUN: %clangxx_asan -O0 %s %p/Helpers/initialization-constexpr-extra.cc --std=c++11 -o %t
|
|
// RUN: env ASAN_OPTIONS=check_initialization_order=true %run %t 2>&1
|
|
// RUN: %clangxx_asan -O1 %s %p/Helpers/initialization-constexpr-extra.cc --std=c++11 -o %t
|
|
// RUN: env ASAN_OPTIONS=check_initialization_order=true %run %t 2>&1
|
|
// RUN: %clangxx_asan -O2 %s %p/Helpers/initialization-constexpr-extra.cc --std=c++11 -o %t
|
|
// RUN: env ASAN_OPTIONS=check_initialization_order=true %run %t 2>&1
|
|
// RUN: %clangxx_asan -O3 %s %p/Helpers/initialization-constexpr-extra.cc --std=c++11 -o %t
|
|
// RUN: env ASAN_OPTIONS=check_initialization_order=true %run %t 2>&1
|
|
|
|
class Integer {
|
|
private:
|
|
int value;
|
|
|
|
public:
|
|
constexpr Integer(int x = 0) : value(x) {}
|
|
int getValue() {return value;}
|
|
};
|
|
Integer coolestInteger(42);
|
|
int getCoolestInteger() { return coolestInteger.getValue(); }
|
|
|
|
int main() { return 0; }
|