maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/Instrumentation/DataFlowSanitizer/args-unreachable-bb.ll

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

32 lines
713 B
LLVM
Raw Normal View History

DataFlowSanitizer: Remove unreachable BBs so IR continues to verify under the args ABI. Differential Revision: http://llvm-reviews.chandlerc.com/D1316 llvm-svn: 188113
2013-08-10 05:42:53 +08:00
; RUN: opt < %s -dfsan -verify -dfsan-args-abi -S | FileCheck %s
target 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-S128"
Add target triples to all dfsan tests. llvm-svn: 223536
2014-12-06 06:32:30 +08:00
target triple = "x86_64-unknown-linux-gnu"
DataFlowSanitizer: Remove unreachable BBs so IR continues to verify under the args ABI. Differential Revision: http://llvm-reviews.chandlerc.com/D1316 llvm-svn: 188113
2013-08-10 05:42:53 +08:00
DataFlowSanitizer: Prefix the name of each instrumented function with "dfs$". DFSan changes the ABI of each function in the module. This makes it possible for a function with the native ABI to be called with the instrumented ABI, or vice versa, thus possibly invoking undefined behavior. A simple way of statically detecting instances of this problem is to prepend the prefix "dfs$" to the name of each instrumented-ABI function. This will not catch every such problem; in particular function pointers passed across the instrumented-native barrier cannot be used on the other side. These problems could potentially be caught dynamically. Differential Revision: http://llvm-reviews.chandlerc.com/D1373 llvm-svn: 189052
2013-08-23 04:08:08 +08:00
; CHECK-LABEL: @"dfs$unreachable_bb1"
Reapply r188119 now that the bug it exposed is fixed. llvm-svn: 188217
2013-08-13 06:38:43 +08:00
define i8 @unreachable_bb1() {
DataFlowSanitizer: Remove unreachable BBs so IR continues to verify under the args ABI. Differential Revision: http://llvm-reviews.chandlerc.com/D1316 llvm-svn: 188113
2013-08-10 05:42:53 +08:00
; CHECK: ret { i8, i16 } { i8 1, i16 0 }
; CHECK-NOT: bb2:
; CHECK-NOT: bb3:
; CHECK-NOT: bb4:
ret i8 1
bb2:
ret i8 2
bb3:
br label %bb4
bb4:
br label %bb3
}
Reapply r188119 now that the bug it exposed is fixed. llvm-svn: 188217
2013-08-13 06:38:43 +08:00
declare void @abort() noreturn
DataFlowSanitizer: Prefix the name of each instrumented function with "dfs$". DFSan changes the ABI of each function in the module. This makes it possible for a function with the native ABI to be called with the instrumented ABI, or vice versa, thus possibly invoking undefined behavior. A simple way of statically detecting instances of this problem is to prepend the prefix "dfs$" to the name of each instrumented-ABI function. This will not catch every such problem; in particular function pointers passed across the instrumented-native barrier cannot be used on the other side. These problems could potentially be caught dynamically. Differential Revision: http://llvm-reviews.chandlerc.com/D1373 llvm-svn: 189052
2013-08-23 04:08:08 +08:00
; CHECK-LABEL: @"dfs$unreachable_bb2"
Reapply r188119 now that the bug it exposed is fixed. llvm-svn: 188217
2013-08-13 06:38:43 +08:00
define i8 @unreachable_bb2() {
call void @abort() noreturn
; CHECK-NOT: i8 12
; CHECK: unreachable
ret i8 12
}