diff options
| author | Teresa Johnson <tejohnson@google.com> | 2023-12-06 08:41:44 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-12-06 08:41:44 -0800 |
| commit | 88fbc4d3df7c24105eb36232ff6250da95c8a202 (patch) | |
| tree | 4bc633dafcb36d16958bf88510d83b3d3ce7e913 /llvm/test/Bitcode/thinlto-function-summary-paramaccess.ll | |
| parent | 8186e1500b1d9709f10199b7c599274f8a6f8e3a (diff) | |
[ThinLTO] Add tail call flag to call edges in summary (#74043)
This adds support for a HasTailCall flag on function call edges in the
ThinLTO summary. It is intended for use in aiding discovery of missing
frames from tail calls in profiled call stacks for MemProf of profiled
binaries that did not disable tail call elimination. A follow on change
will add the use of this new flag during MemProf context disambiguation.
The new flag is encoded in the bitcode along with either the hotness
flag from the profile, or the relative block frequency under the
-write-relbf-to-summary flag when there is no profile data.
Because we now will always have some additional call edge information, I
have removed the non-profile function summary record format, and we
simply encode the tail call flag along with a hotness type of none when
there is no profile information or relative block frequency. The change
of record format and name caused most of the test case changes.
I have added explicit testing of generation of the new tail call flag
into the bitcode and IR assembly format as part of the changes to
llvm/test/Bitcode/thinlto-function-summary-refgraph.ll. I have also
added round trip testing through assembly and bitcode to
llvm/test/Assembler/thinlto-summary.ll.
Diffstat (limited to 'llvm/test/Bitcode/thinlto-function-summary-paramaccess.ll')
| -rw-r--r-- | llvm/test/Bitcode/thinlto-function-summary-paramaccess.ll | 38 |
1 files changed, 19 insertions, 19 deletions
diff --git a/llvm/test/Bitcode/thinlto-function-summary-paramaccess.ll b/llvm/test/Bitcode/thinlto-function-summary-paramaccess.ll index 96a783fdb3e2..f8e6476ea3e8 100644 --- a/llvm/test/Bitcode/thinlto-function-summary-paramaccess.ll +++ b/llvm/test/Bitcode/thinlto-function-summary-paramaccess.ll @@ -306,35 +306,35 @@ entry: ; COMBINED-NEXT: <VALUE_GUID op0=18 op1=-1792695732907084926/> ; COMBINED-NEXT: <VALUE_GUID op0=19 op1=-1296325529848142540/> ; COMBINED-NEXT: <PARAM_ACCESS op0=1 op1=0 op2=0 op3=0/> -; COMBINED-NEXT: <COMBINED abbrevid=4 op0=1 +; COMBINED-NEXT: <COMBINED_PROFILE abbrevid=4 op0=1 ; COMBINED-NEXT: <PARAM_ACCESS op0=0 op1=0 op2=0 op3=0/> -; COMBINED-NEXT: <COMBINED abbrevid=4 op0=2 +; COMBINED-NEXT: <COMBINED_PROFILE abbrevid=4 op0=2 ; COMBINED-NEXT: <PARAM_ACCESS op0=0 op1=0 op2=0 op3=1 op4=0 op5=[[CALLEE2]] op6=4 op7=6/> -; COMBINED-NEXT: <COMBINED abbrevid=4 op0=3 +; COMBINED-NEXT: <COMBINED_PROFILE abbrevid=4 op0=3 ; COMBINED-NEXT: <PARAM_ACCESS op0=0 op1=24 op2=32 op3=0/> -; COMBINED-NEXT: <COMBINED abbrevid=4 op0=4 +; COMBINED-NEXT: <COMBINED_PROFILE abbrevid=4 op0=4 ; COMBINED-NEXT: <PARAM_ACCESS op0=0 op1=0 op2=2 op3=0 op4=2 op5=0 op6=8 op7=0/> -; COMBINED-NEXT: <COMBINED abbrevid=4 op0=5 -; COMBINED-NEXT: <COMBINED abbrevid=4 op0=6 +; COMBINED-NEXT: <COMBINED_PROFILE abbrevid=4 op0=5 +; COMBINED-NEXT: <COMBINED_PROFILE abbrevid=4 op0=6 ; COMBINED-NEXT: <PARAM_ACCESS op0=0 op1=0 op2=2 op3=0/> -; COMBINED-NEXT: <COMBINED abbrevid=4 op0=7 +; COMBINED-NEXT: <COMBINED_PROFILE abbrevid=4 op0=7 ; COMBINED-NEXT: <PARAM_ACCESS op0=0 op1=0 op2=2 op3=0 op4=1 op5=0 op6=8 op7=0/> -; COMBINED-NEXT: <COMBINED abbrevid=4 op0=8 -; COMBINED-NEXT: <COMBINED abbrevid=4 op0=9 +; COMBINED-NEXT: <COMBINED_PROFILE abbrevid=4 op0=8 +; COMBINED-NEXT: <COMBINED_PROFILE abbrevid=4 op0=9 ; COMBINED-NEXT: <PARAM_ACCESS op0=0 op1=0 op2=0 op3=1 op4=0 op5=[[CALLEE2]] op6=0 op7=2/> -; COMBINED-NEXT: <COMBINED abbrevid=4 op0=10 -; COMBINED-NEXT: <COMBINED abbrevid=4 op0=11 +; COMBINED-NEXT: <COMBINED_PROFILE abbrevid=4 op0=10 +; COMBINED-NEXT: <COMBINED_PROFILE abbrevid=4 op0=11 ; COMBINED-NEXT: <PARAM_ACCESS op0=0 op1=113 op2=97 op3=0/> -; COMBINED-NEXT: <COMBINED abbrevid=4 op0=12 -; COMBINED-NEXT: <COMBINED abbrevid=4 op0=13 +; COMBINED-NEXT: <COMBINED_PROFILE abbrevid=4 op0=12 +; COMBINED-NEXT: <COMBINED_PROFILE abbrevid=4 op0=13 ; COMBINED-NEXT: <PARAM_ACCESS op0=0 op1=0 op2=0 op3=0/> -; COMBINED-NEXT: <COMBINED abbrevid=4 op0=14 -; COMBINED-NEXT: <COMBINED abbrevid=4 op0=15 +; COMBINED-NEXT: <COMBINED_PROFILE abbrevid=4 op0=14 +; COMBINED-NEXT: <COMBINED_PROFILE abbrevid=4 op0=15 ; COMBINED-NEXT: <PARAM_ACCESS op0=0 op1=1 op2=-2 op3=0/> -; COMBINED-NEXT: <COMBINED abbrevid=4 op0=16 +; COMBINED-NEXT: <COMBINED_PROFILE abbrevid=4 op0=16 ; COMBINED-NEXT: <PARAM_ACCESS op0=0 op1=0 op2=0 op3=1 op4=0 op5=[[CALLEE2]] op6=1431 op7=1429/> -; COMBINED-NEXT: <COMBINED abbrevid=4 op0=17 +; COMBINED-NEXT: <COMBINED_PROFILE abbrevid=4 op0=17 ; COMBINED-NEXT: <PARAM_ACCESS op0=0 op1=0 op2=0 op3=2 op4=0 op5=[[CALLEE2]] op6=1431 op7=250 op8=1 op9=[[CALLEE1]] op10=67 op11=65/> -; COMBINED-NEXT: <COMBINED abbrevid=4 op0=18 +; COMBINED-NEXT: <COMBINED_PROFILE abbrevid=4 op0=18 ; COMBINED-NEXT: <PARAM_ACCESS op0=0 op1=0 op2=0 op3=1 op4=0 op5=[[CALLEE2]] op6=1431 op7=250/> -; COMBINED-NEXT: <COMBINED abbrevid=4 op0=19 +; COMBINED-NEXT: <COMBINED_PROFILE abbrevid=4 op0=19 |