27 lines · plain
1; Check that sanitizers invalidate GlobalsAA2 3; Msan and Dfsan use globals for origin tracking and TLS for parameters.4; RUN: opt < %s -S -passes='require<globals-aa>,module(msan)' -debug-pass-manager 2>&1 | FileCheck %s5; RUN: opt < %s -S -passes='require<globals-aa>,module(dfsan)' -debug-pass-manager 2>&1 | FileCheck %s6 7; Some types of coverage use globals.8; RUN: opt < %s -S -passes='require<globals-aa>,module(sancov-module)' -sanitizer-coverage-level=2 -debug-pass-manager 2>&1 | FileCheck %s9 10; Uses TLS for tags.11; RUN: opt < %s -S -passes='require<globals-aa>,module(hwasan)' -debug-pass-manager 2>&1 | FileCheck %s12 13; Modifies globals.14; RUN: opt < %s -S -passes='require<globals-aa>,module(asan)' -debug-pass-manager 2>&1 | FileCheck %s15 16; CHECK: Running analysis: GlobalsAA on [module]17; CHECK: Running pass: {{.*}}Sanitizer{{.*}}Pass on [module]18; CHECK: Invalidating analysis: GlobalsAA on [module]19 20target triple = "x86_64-unknown-linux"21 22define i32 @test(ptr readonly %a) local_unnamed_addr sanitize_address sanitize_hwaddress {23entry:24 %0 = load i32, ptr %a, align 425 ret i32 %026}27