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
45 lines
1.9 KiB
LLVM
45 lines
1.9 KiB
LLVM
; Test to check the callgraph in summary when there is PGO
|
|
; RUN: llvm-as -function-summary %s -o %t.o
|
|
; RUN: llvm-bcanalyzer -dump %t.o | FileCheck %s
|
|
; RUN: llvm-as -function-summary %p/Inputs/thinlto-function-summary-callgraph.ll -o %t2.o
|
|
; RUN: llvm-lto -thinlto -o %t3 %t.o %t2.o
|
|
; RUN: llvm-bcanalyzer -dump %t3.thinlto.bc | FileCheck %s --check-prefix=COMBINED
|
|
|
|
; CHECK: <GLOBALVAL_SUMMARY_BLOCK
|
|
; See if the call to func is registered, using the expected callsite count
|
|
; and profile count, with value id matching the subsequent value symbol table.
|
|
; CHECK-NEXT: <PERMODULE_PROFILE {{.*}} op4=[[FUNCID:[0-9]+]] op5=1 op6=1/>
|
|
; CHECK-NEXT: </GLOBALVAL_SUMMARY_BLOCK>
|
|
; CHECK-NEXT: <VALUE_SYMTAB
|
|
; CHECK-NEXT: <FNENTRY {{.*}} record string = 'main'
|
|
; External function func should have entry with value id FUNCID
|
|
; CHECK-NEXT: <ENTRY {{.*}} op0=[[FUNCID]] {{.*}} record string = 'func'
|
|
; CHECK-NEXT: </VALUE_SYMTAB>
|
|
|
|
; COMBINED: <GLOBALVAL_SUMMARY_BLOCK
|
|
; COMBINED-NEXT: <COMBINED
|
|
; See if the call to func is registered, using the expected callsite count
|
|
; and profile count, with value id matching the subsequent value symbol table.
|
|
; COMBINED-NEXT: <COMBINED_PROFILE {{.*}} op4=[[FUNCID:[0-9]+]] op5=1 op6=1/>
|
|
; COMBINED-NEXT: </GLOBALVAL_SUMMARY_BLOCK>
|
|
; COMBINED-NEXT: <VALUE_SYMTAB
|
|
; Entry for function func should have entry with value id FUNCID
|
|
; COMBINED-NEXT: <COMBINED_GVDEFENTRY {{.*}} op0=[[FUNCID]] {{.*}} op2=7289175272376759421/>
|
|
; COMBINED-NEXT: <COMBINED_GVDEFENTRY
|
|
; COMBINED-NEXT: </VALUE_SYMTAB>
|
|
|
|
; ModuleID = 'thinlto-function-summary-callgraph.ll'
|
|
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
|
|
target triple = "x86_64-unknown-linux-gnu"
|
|
|
|
; Function Attrs: nounwind uwtable
|
|
define i32 @main() #0 !prof !2 {
|
|
entry:
|
|
call void (...) @func()
|
|
ret i32 0
|
|
}
|
|
|
|
declare void @func(...) #1
|
|
|
|
!2 = !{!"function_entry_count", i64 1}
|