1; Test that AddressSanitizer instruments "(*a)++" only once. 2; RUN: opt < %s -asan -asan-module -enable-new-pm=0 -S -asan-opt=1 | FileCheck %s -check-prefix=OPT1 3; RUN: opt < %s -passes='asan-pipeline' -S -asan-opt=1 | FileCheck %s -check-prefix=OPT1 4; RUN: opt < %s -asan -asan-module -enable-new-pm=0 -S -asan-opt=0 | FileCheck %s -check-prefix=OPT0 5; RUN: opt < %s -passes='asan-pipeline' -S -asan-opt=0 | FileCheck %s -check-prefix=OPT0 6 7target datalayout = "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64" 8target triple = "x86_64-unknown-linux-gnu" 9define void @IncrementMe(i32* %a) sanitize_address { 10entry: 11 %tmp1 = load i32, i32* %a, align 4 12 %tmp2 = add i32 %tmp1, 1 13 store i32 %tmp2, i32* %a, align 4 14 ret void 15} 16 17; With optimizations enabled we should see only one call to __asan_report_* 18; OPT1: IncrementMe 19; OPT1: __asan_report_ 20; OPT1-NOT: __asan_report_ 21; OPT1: ret void 22 23; Without optimizations we should see two calls to __asan_report_* 24; OPT0: IncrementMe 25; OPT0: __asan_report_ 26; OPT0: __asan_report_ 27; OPT0: ret void 28