2016-02-10 06:50:34 +08:00
|
|
|
; RUN: opt -S -wholeprogramdevirt %s | FileCheck %s
|
2017-02-18 02:17:04 +08:00
|
|
|
; RUN: opt -S -passes=wholeprogramdevirt %s | FileCheck %s
|
2016-02-10 06:50:34 +08:00
|
|
|
|
|
|
|
target datalayout = "e-p:64:64"
|
|
|
|
target triple = "x86_64-unknown-linux-gnu"
|
|
|
|
|
2017-02-18 02:17:04 +08:00
|
|
|
@vt1 = constant [2 x i8*] [i8* bitcast (i32 (i8*, i32)* @vf1a to i8*), i8* bitcast (i32 (i8*, i32)* @vf1b to i8*)], !type !0
|
|
|
|
@vt2 = constant [2 x i8*] [i8* bitcast (i32 (i8*, i32)* @vf2a to i8*), i8* bitcast (i32 (i8*, i32)* @vf2b to i8*)], !type !0
|
2016-02-10 06:50:34 +08:00
|
|
|
|
2017-02-18 02:17:04 +08:00
|
|
|
@sink = external global i32
|
|
|
|
|
|
|
|
define i32 @vf1a(i8* %this, i32 %arg) {
|
|
|
|
store i32 %arg, i32* @sink
|
|
|
|
ret i32 %arg
|
|
|
|
}
|
|
|
|
|
|
|
|
define i32 @vf2a(i8* %this, i32 %arg) {
|
|
|
|
store i32 %arg, i32* @sink
|
|
|
|
ret i32 %arg
|
|
|
|
}
|
|
|
|
|
|
|
|
define i32 @vf1b(i8* %this, i32 %arg) {
|
2016-02-10 06:50:34 +08:00
|
|
|
ret i32 %arg
|
|
|
|
}
|
|
|
|
|
2017-02-18 02:17:04 +08:00
|
|
|
define i32 @vf2b(i8* %this, i32 %arg) {
|
2016-02-10 06:50:34 +08:00
|
|
|
ret i32 %arg
|
|
|
|
}
|
|
|
|
|
2017-02-18 02:17:04 +08:00
|
|
|
; Test that we don't apply VCP if the virtual function body accesses memory,
|
|
|
|
; even if the function returns a constant.
|
|
|
|
|
|
|
|
; CHECK: define i32 @call1
|
|
|
|
define i32 @call1(i8* %obj) {
|
2016-02-10 06:50:34 +08:00
|
|
|
%vtableptr = bitcast i8* %obj to [1 x i8*]**
|
|
|
|
%vtable = load [1 x i8*]*, [1 x i8*]** %vtableptr
|
|
|
|
%vtablei8 = bitcast [1 x i8*]* %vtable to i8*
|
IR: New representation for CFI and virtual call optimization pass metadata.
The bitset metadata currently used in LLVM has a few problems:
1. It has the wrong name. The name "bitset" refers to an implementation
detail of one use of the metadata (i.e. its original use case, CFI).
This makes it harder to understand, as the name makes no sense in the
context of virtual call optimization.
2. It is represented using a global named metadata node, rather than
being directly associated with a global. This makes it harder to
manipulate the metadata when rebuilding global variables, summarise it
as part of ThinLTO and drop unused metadata when associated globals are
dropped. For this reason, CFI does not currently work correctly when
both CFI and vcall opt are enabled, as vcall opt needs to rebuild vtable
globals, and fails to associate metadata with the rebuilt globals. As I
understand it, the same problem could also affect ASan, which rebuilds
globals with a red zone.
This patch solves both of those problems in the following way:
1. Rename the metadata to "type metadata". This new name reflects how
the metadata is currently being used (i.e. to represent type information
for CFI and vtable opt). The new name is reflected in the name for the
associated intrinsic (llvm.type.test) and pass (LowerTypeTests).
2. Attach metadata directly to the globals that it pertains to, rather
than using the "llvm.bitsets" global metadata node as we are doing now.
This is done using the newly introduced capability to attach
metadata to global variables (r271348 and r271358).
See also: http://lists.llvm.org/pipermail/llvm-dev/2016-June/100462.html
Differential Revision: http://reviews.llvm.org/D21053
llvm-svn: 273729
2016-06-25 05:21:32 +08:00
|
|
|
%p = call i1 @llvm.type.test(i8* %vtablei8, metadata !"typeid")
|
2016-02-10 06:50:34 +08:00
|
|
|
call void @llvm.assume(i1 %p)
|
|
|
|
%fptrptr = getelementptr [1 x i8*], [1 x i8*]* %vtable, i32 0, i32 0
|
|
|
|
%fptr = load i8*, i8** %fptrptr
|
|
|
|
%fptr_casted = bitcast i8* %fptr to i32 (i8*, i32)*
|
|
|
|
; CHECK: call i32 %
|
|
|
|
%result = call i32 %fptr_casted(i8* %obj, i32 1)
|
|
|
|
ret i32 %result
|
|
|
|
}
|
|
|
|
|
2017-02-18 02:17:04 +08:00
|
|
|
; Test that we can apply VCP regardless of the function attributes by analyzing
|
|
|
|
; the function body itself.
|
|
|
|
|
|
|
|
; CHECK: define i32 @call2
|
|
|
|
define i32 @call2(i8* %obj) {
|
|
|
|
%vtableptr = bitcast i8* %obj to [1 x i8*]**
|
|
|
|
%vtable = load [1 x i8*]*, [1 x i8*]** %vtableptr
|
|
|
|
%vtablei8 = bitcast [1 x i8*]* %vtable to i8*
|
|
|
|
%p = call i1 @llvm.type.test(i8* %vtablei8, metadata !"typeid")
|
|
|
|
call void @llvm.assume(i1 %p)
|
|
|
|
%fptrptr = getelementptr [1 x i8*], [1 x i8*]* %vtable, i32 0, i32 1
|
|
|
|
%fptr = load i8*, i8** %fptrptr
|
|
|
|
%fptr_casted = bitcast i8* %fptr to i32 (i8*, i32)*
|
|
|
|
%result = call i32 %fptr_casted(i8* %obj, i32 1)
|
|
|
|
; CHECK: ret i32 1
|
|
|
|
ret i32 %result
|
|
|
|
}
|
|
|
|
|
IR: New representation for CFI and virtual call optimization pass metadata.
The bitset metadata currently used in LLVM has a few problems:
1. It has the wrong name. The name "bitset" refers to an implementation
detail of one use of the metadata (i.e. its original use case, CFI).
This makes it harder to understand, as the name makes no sense in the
context of virtual call optimization.
2. It is represented using a global named metadata node, rather than
being directly associated with a global. This makes it harder to
manipulate the metadata when rebuilding global variables, summarise it
as part of ThinLTO and drop unused metadata when associated globals are
dropped. For this reason, CFI does not currently work correctly when
both CFI and vcall opt are enabled, as vcall opt needs to rebuild vtable
globals, and fails to associate metadata with the rebuilt globals. As I
understand it, the same problem could also affect ASan, which rebuilds
globals with a red zone.
This patch solves both of those problems in the following way:
1. Rename the metadata to "type metadata". This new name reflects how
the metadata is currently being used (i.e. to represent type information
for CFI and vtable opt). The new name is reflected in the name for the
associated intrinsic (llvm.type.test) and pass (LowerTypeTests).
2. Attach metadata directly to the globals that it pertains to, rather
than using the "llvm.bitsets" global metadata node as we are doing now.
This is done using the newly introduced capability to attach
metadata to global variables (r271348 and r271358).
See also: http://lists.llvm.org/pipermail/llvm-dev/2016-June/100462.html
Differential Revision: http://reviews.llvm.org/D21053
llvm-svn: 273729
2016-06-25 05:21:32 +08:00
|
|
|
declare i1 @llvm.type.test(i8*, metadata)
|
2016-02-10 06:50:34 +08:00
|
|
|
declare void @llvm.assume(i1)
|
|
|
|
|
IR: New representation for CFI and virtual call optimization pass metadata.
The bitset metadata currently used in LLVM has a few problems:
1. It has the wrong name. The name "bitset" refers to an implementation
detail of one use of the metadata (i.e. its original use case, CFI).
This makes it harder to understand, as the name makes no sense in the
context of virtual call optimization.
2. It is represented using a global named metadata node, rather than
being directly associated with a global. This makes it harder to
manipulate the metadata when rebuilding global variables, summarise it
as part of ThinLTO and drop unused metadata when associated globals are
dropped. For this reason, CFI does not currently work correctly when
both CFI and vcall opt are enabled, as vcall opt needs to rebuild vtable
globals, and fails to associate metadata with the rebuilt globals. As I
understand it, the same problem could also affect ASan, which rebuilds
globals with a red zone.
This patch solves both of those problems in the following way:
1. Rename the metadata to "type metadata". This new name reflects how
the metadata is currently being used (i.e. to represent type information
for CFI and vtable opt). The new name is reflected in the name for the
associated intrinsic (llvm.type.test) and pass (LowerTypeTests).
2. Attach metadata directly to the globals that it pertains to, rather
than using the "llvm.bitsets" global metadata node as we are doing now.
This is done using the newly introduced capability to attach
metadata to global variables (r271348 and r271358).
See also: http://lists.llvm.org/pipermail/llvm-dev/2016-June/100462.html
Differential Revision: http://reviews.llvm.org/D21053
llvm-svn: 273729
2016-06-25 05:21:32 +08:00
|
|
|
!0 = !{i32 0, !"typeid"}
|