2016-04-26 13:59:08 +08:00
|
|
|
; RUN: llvm-as < %s | llvm-bcanalyzer -dump -disable-histogram | FileCheck %s
|
|
|
|
|
|
|
|
|
|
; CHECK: <OPERAND_BUNDLE_TAGS_BLOCK
|
|
|
|
|
; CHECK-NEXT: <OPERAND_BUNDLE_TAG
|
|
|
|
|
; CHECK-NEXT: <OPERAND_BUNDLE_TAG
|
|
|
|
|
; CHECK-NEXT: <OPERAND_BUNDLE_TAG
|
|
|
|
|
; CHECK-NEXT: <OPERAND_BUNDLE_TAG
|
|
|
|
|
; CHECK-NEXT: <OPERAND_BUNDLE_TAG
|
Add Windows Control Flow Guard checks (/guard:cf).
Summary:
A new function pass (Transforms/CFGuard/CFGuard.cpp) inserts CFGuard checks on
indirect function calls, using either the check mechanism (X86, ARM, AArch64) or
or the dispatch mechanism (X86-64). The check mechanism requires a new calling
convention for the supported targets. The dispatch mechanism adds the target as
an operand bundle, which is processed by SelectionDAG. Another pass
(CodeGen/CFGuardLongjmp.cpp) identifies and emits valid longjmp targets, as
required by /guard:cf. This feature is enabled using the `cfguard` CC1 option.
Reviewers: thakis, rnk, theraven, pcc
Subscribers: ychen, hans, metalcanine, dmajor, tomrittervg, alex, mehdi_amini, mgorny, javed.absar, kristof.beyls, hiraditya, steven_wu, dexonsmith, cfe-commits, llvm-commits
Tags: #clang, #llvm
Differential Revision: https://reviews.llvm.org/D65761
2019-10-28 21:22:19 +08:00
|
|
|
; CHECK-NEXT: <OPERAND_BUNDLE_TAG
|
2016-04-26 13:59:08 +08:00
|
|
|
; CHECK-NEXT: </OPERAND_BUNDLE_TAGS_BLOCK
|
|
|
|
|
|
|
|
|
|
; CHECK: <FUNCTION_BLOCK
|
|
|
|
|
; CHECK: <OPERAND_BUNDLE
|
|
|
|
|
; CHECK: <OPERAND_BUNDLE
|
|
|
|
|
; CHECK-NOT: <OPERAND_BUNDLE
|
|
|
|
|
; CHECK: </FUNCTION_BLOCK
|
|
|
|
|
|
|
|
|
|
; CHECK: Block ID #{{[0-9]+}} (OPERAND_BUNDLE_TAGS_BLOCK)
|
|
|
|
|
|
|
|
|
|
declare void @callee0()
|
|
|
|
|
|
|
|
|
|
define void @f0(i32* %ptr) {
|
|
|
|
|
entry:
|
|
|
|
|
%l = load i32, i32* %ptr
|
|
|
|
|
%x = add i32 42, 1
|
|
|
|
|
call void @callee0() [ "foo"(i32 42, i64 100, i32 %x), "bar"(float 0.000000e+00, i64 100, i32 %l) ]
|
|
|
|
|
ret void
|
|
|
|
|
}
|
