2016-03-15 08:04:37 +08:00
|
|
|
; RUN: llvm-as -module-summary < %s | llvm-bcanalyzer -dump | FileCheck %s -check-prefix=BC
|
|
|
|
; Check for summary block/records.
|
2015-10-04 22:33:43 +08:00
|
|
|
|
2016-03-15 08:04:37 +08:00
|
|
|
; Check the value ids in the summary entries against the
|
2016-02-02 07:26:30 +08:00
|
|
|
; same in the ValueSumbolTable, to ensure the ordering is stable.
|
2016-02-07 00:07:35 +08:00
|
|
|
; Also check the linkage field on the summary entries.
|
[ThinLTO] Support for reference graph in per-module and combined summary.
Summary:
This patch adds support for including a full reference graph including
call graph edges and other GV references in the summary.
The reference graph edges can be used to make importing decisions
without materializing any source modules, can be used in the plugin
to make file staging decisions for distributed build systems, and is
expected to have other uses.
The call graph edges are recorded in each function summary in the
bitcode via a list of <CalleeValueIds, StaticCount> tuples when no PGO
data exists, or <CalleeValueId, StaticCount, ProfileCount> pairs when
there is PGO, where the ValueId can be mapped to the function GUID via
the ValueSymbolTable. In the function index in memory, the call graph
edges reference the target via the CalleeGUID instead of the
CalleeValueId.
The reference graph edges are recorded in each summary record with a
list of referenced value IDs, which can be mapped to value GUID via the
ValueSymbolTable.
Addtionally, a new summary record type is added to record references
from global variable initializers. A number of bitcode records and data
structures have been renamed to reflect the newly expanded scope of the
summary beyond functions. More cleanup will follow.
Reviewers: joker.eph, davidxl
Subscribers: joker.eph, llvm-commits
Differential Revision: http://reviews.llvm.org/D17212
llvm-svn: 263275
2016-03-12 02:52:24 +08:00
|
|
|
; BC: <GLOBALVAL_SUMMARY_BLOCK
|
|
|
|
; BC-NEXT: <PERMODULE {{.*}} op0=1 op1=0
|
|
|
|
; BC-NEXT: <PERMODULE {{.*}} op0=2 op1=0
|
|
|
|
; BC-NEXT: <PERMODULE {{.*}} op0=4 op1=3
|
|
|
|
; BC-NEXT: </GLOBALVAL_SUMMARY_BLOCK
|
2016-02-02 07:26:30 +08:00
|
|
|
; BC-NEXT: <VALUE_SYMTAB
|
|
|
|
; BC-NEXT: <FNENTRY {{.*}} op0=1 {{.*}}> record string = 'foo'
|
|
|
|
; BC-NEXT: <FNENTRY {{.*}} op0=2 {{.*}}> record string = 'bar'
|
|
|
|
; BC-NEXT: <FNENTRY {{.*}} op0=4 {{.*}}> record string = 'f'
|
2015-10-04 22:33:43 +08:00
|
|
|
|
2016-03-15 08:04:37 +08:00
|
|
|
; RUN: llvm-as -module-summary < %s | llvm-dis | FileCheck %s
|
2015-10-04 22:33:43 +08:00
|
|
|
; Check that this round-trips correctly.
|
|
|
|
|
|
|
|
; ModuleID = '<stdin>'
|
|
|
|
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
|
|
|
|
target triple = "x86_64-unknown-linux-gnu"
|
|
|
|
|
|
|
|
; CHECK: define i32 @foo()
|
|
|
|
|
|
|
|
; Function Attrs: nounwind uwtable
|
|
|
|
define i32 @foo() #0 {
|
|
|
|
entry:
|
|
|
|
ret i32 1
|
|
|
|
}
|
|
|
|
|
|
|
|
; CHECK: define i32 @bar(i32 %x)
|
|
|
|
|
|
|
|
; Function Attrs: nounwind uwtable
|
|
|
|
define i32 @bar(i32 %x) #0 {
|
|
|
|
entry:
|
|
|
|
ret i32 %x
|
|
|
|
}
|
|
|
|
|
|
|
|
; Check an anonymous function as well, since in that case only the alias
|
|
|
|
; ends up in the value symbol table and having a summary.
|
|
|
|
@f = alias void (), void ()* @0 ; <void ()*> [#uses=0]
|
|
|
|
@h = external global void ()* ; <void ()*> [#uses=0]
|
|
|
|
|
|
|
|
define internal void @0() nounwind {
|
|
|
|
entry:
|
|
|
|
store void()* @0, void()** @h
|
|
|
|
br label %return
|
|
|
|
|
|
|
|
return: ; preds = %entry
|
|
|
|
ret void
|
|
|
|
}
|