diff options
Diffstat (limited to 'test/CodeGen/asan-strings.c')
| -rw-r--r-- | test/CodeGen/asan-strings.c | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/test/CodeGen/asan-strings.c b/test/CodeGen/asan-strings.c new file mode 100644 index 0000000000000..fc9c31bcd8a25 --- /dev/null +++ b/test/CodeGen/asan-strings.c @@ -0,0 +1,17 @@ +// RUN: %clang_cc1 -triple x86_64-linux-gnu -fsanitize=address -disable-llvm-passes -emit-llvm -o - %s | FileCheck %s --check-prefix=LINUX +// RUN: %clang_cc1 -triple x86_64-windows-msvc -fsanitize=address -disable-llvm-passes -emit-llvm -o - %s | FileCheck %s --check-prefix=WINDOWS +// RUN: %clang_cc1 -triple x86_64-windows-msvc -fsanitize=address -fwritable-strings -disable-llvm-passes -emit-llvm -o - %s | FileCheck %s --check-prefix=WINWRITE + +// On Linux (and basically every non-MS target) string literals are emitted with +// private linkage, which means ASan can freely instrument them. On Windows, +// they are emitted with comdats. ASan's global instrumentation code for COFF +// knows how to make the metadata comdat associative, so the string literal +// global is only registered if the instrumented global prevails during linking. + +const char *foo() { return "asdf"; } + +// LINUX: @.str = private unnamed_addr constant [5 x i8] c"asdf\00", align 1 + +// WINDOWS: @"??_C@_04JIHMPGLA@asdf?$AA@" = linkonce_odr dso_local unnamed_addr constant [5 x i8] c"asdf\00", comdat, align 1 + +// WINWRITE: @.str = private unnamed_addr global [5 x i8] c"asdf\00", align 1 |