-
Notifications
You must be signed in to change notification settings - Fork 14.8k
[clang] Introduce CallGraphSection codegen option #117037
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Prabhuk
merged 107 commits into
main
from
users/Prabhuk/sprclangcallgraphsection-add-call-graph-section-option-and-docs
Oct 11, 2025
Merged
Changes from 2 commits
Commits
Show all changes
107 commits
Select commit
Hold shift + click to select a range
29d4db2
[𝘀𝗽𝗿] changes to main this commit is based on
Prabhuk 8f53618
[𝘀𝗽𝗿] initial version
Prabhuk a794047
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil abfcb9c
Reorder commits.
Prabhuk de23806
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 05307cf
Update LTO compilation CodeGen flag for call-graph-section.
Prabhuk 6a12be2
Fix EOF newlines.
Prabhuk a068971
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 54a3db2
Add requested tests part 1.
Prabhuk 74044aa
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 77672ec
Update comments in tests.
Prabhuk 1826b03
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil a8e2bd8
Updated the test as reviewers suggested.
Prabhuk 2f7dbf2
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 3b605a6
Scoped enum. Simplify test.
Prabhuk 7014fef
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil db11fc7
Remove unnecessary cast.
Prabhuk eb582bd
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 673481e
Remove unnecessary asserts. Remove autos for better readability.
Prabhuk 6388364
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 694cfd0
Reorder IR metadata and rename temporary var names in test.
Prabhuk f90b397
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 270074f
Add RISC-V support. Clean up test files.
Prabhuk da8ae04
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 6045320
Clean up test files.
Prabhuk 573eebe
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil a175709
Address review comments.
Prabhuk 823a513
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil b5b2b10
Use callee_type metadata instead of OB.
Prabhuk 2cac836
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 5ede050
Address review comments.
Prabhuk 0c78d0a
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil d0a96ac
Rebase on top of llvm stack.
Prabhuk 7a1c8fb
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 89c896b
Rebase on parent llvm change.
Prabhuk a56ccb8
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil c53d51d
Address review comments.
Prabhuk ab46191
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 839da25
Address review comments.
Prabhuk 5b36796
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 43d6eed
Rebase on parent.
Prabhuk 05057b8
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 5188f32
Rebase on parent.
Prabhuk 2131b83
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil c5a12e9
Rebase on parent.
Prabhuk 759a709
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 5cdb84e
Rebase on llvm changes.
Prabhuk 32c7adb
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 75dec8e
Rebase on parent.
Prabhuk 8a289b1
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil e0020f5
Rebase on parent.
Prabhuk 9c21da8
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil f165443
Rebase on parent change.
Prabhuk f83a155
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 2745a8a
Rebase on parent llvm changes.
Prabhuk 03ad07f
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 12df871
Rebase on parent.
Prabhuk edf799d
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 2a3c23d
Rebase on parent
Prabhuk d04642b
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil d4d4533
Rebase on main.
Prabhuk 8bbbe12
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 37d3ef9
Rebase on parent.
Prabhuk ca6d2cc
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil c02cbb9
Rebase change.
Prabhuk 8f07a4c
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil b16770b
Rebase.
Prabhuk 0e29abc
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 1e773e1
Rebase on parent
Prabhuk 38fc4f5
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 7b9cbb3
Rebase on top of main.
Prabhuk b7d5e7f
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 9591c3a
Rebase on parent.
Prabhuk c262b69
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 07f7768
Rebase on parent
Prabhuk 125ddcd
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 15a1b29
Rebase on top of parent change.
Prabhuk 9eff07d
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 1c0f1ab
Rebase on parent.
Prabhuk 1ba8c04
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 0c1ec48
Rebase on parent.
Prabhuk c9f6c5c
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 9592631
Address review comments.
Prabhuk c09082e
[𝘀𝗽𝗿] changes introduced through rebase
necipfazil 80c3580
Rebase on parent.
Prabhuk c67f714
Fix review comment on test file.
Prabhuk 7f95a40
[𝘀𝗽𝗿] changes introduced through rebase
Prabhuk 410bb0d
Rebase.
Prabhuk 7321a3e
[𝘀𝗽𝗿] changes introduced through rebase
Prabhuk 66c858e
Rebase on parent llvm change.
Prabhuk 2d81ecc
[𝘀𝗽𝗿] changes introduced through rebase
Prabhuk c2294fa
Rebase on main.
Prabhuk 571a431
[𝘀𝗽𝗿] changes introduced through rebase
Prabhuk 6884d2a
Rebase.
Prabhuk 036be4e
[𝘀𝗽𝗿] changes introduced through rebase
Prabhuk 1fb27f8
Rebase on parent.
Prabhuk 4ec81ea
[𝘀𝗽𝗿] changes introduced through rebase
Prabhuk 9d29e55
Rebase on llvm changes.
Prabhuk 23c8579
[𝘀𝗽𝗿] changes introduced through rebase
Prabhuk 00f7d91
Rebase on main.
Prabhuk 2924f11
[𝘀𝗽𝗿] changes introduced through rebase
Prabhuk 0aa3d97
Rebase on main.
Prabhuk 50a5786
[𝘀𝗽𝗿] changes introduced through rebase
Prabhuk a6b4a13
Rebase on parent.
Prabhuk f4d6c96
Rebase on main.
Prabhuk d349feb
Make Driver flag experimental.
Prabhuk d50a454
Merge branch 'main' into users/Prabhuk/sprclangcallgraphsection-add-c…
Prabhuk File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,251 @@ | ||
================== | ||
Call Graph Section | ||
================== | ||
|
||
Introduction | ||
============ | ||
|
||
With ``-fcall-graph-section``, the compiler will create a call graph section | ||
in the object file. It will include type identifiers for indirect calls and | ||
targets. This information can be used to map indirect calls to their receivers | ||
with matching types. A complete and high-precision call graph can be | ||
reconstructed by complementing this information with disassembly | ||
(see ``llvm-objdump --call-graph-info``). | ||
|
||
Semantics | ||
========= | ||
|
||
A coarse-grained, type-agnostic call graph may allow indirect calls to target | ||
any function in the program. This approach ensures completeness since no | ||
indirect call edge is missing. However, it is generally poor in precision | ||
due to having unneeded edges. | ||
|
||
A call graph section provides type identifiers for indirect calls and targets. | ||
This information can be used to restrict the receivers of an indirect target to | ||
indirect calls with matching type. Consequently, the precision for indirect | ||
call edges are improved while maintaining the completeness. | ||
|
||
The ``llvm-objdump`` utility provides a ``--call-graph-info`` option to extract | ||
full call graph information by parsing the content of the call graph section | ||
and disassembling the program for complementary information, e.g., direct | ||
calls. | ||
|
||
Section layout | ||
============== | ||
|
||
A call graph section consists of zero or more call graph entries. | ||
Each entry contains information on a function and its indirect calls. | ||
|
||
An entry of a call graph section has the following layout in the binary: | ||
|
||
+---------------------+-----------------------------------------------------------------------+ | ||
| Element | Content | | ||
+=====================+=======================================================================+ | ||
| FormatVersionNumber | Format version number. | | ||
+---------------------+-----------------------------------------------------------------------+ | ||
| FunctionEntryPc | Function entry address. | | ||
+---------------------+-----------------------------------+-----------------------------------+ | ||
| | A flag whether the function is an | - 0: not an indirect target | | ||
| FunctionKind | indirect target, and if so, | - 1: indirect target, unknown id | | ||
| | whether its type id is known. | - 2: indirect target, known id | | ||
+---------------------+-----------------------------------+-----------------------------------+ | ||
| FunctionTypeId | Type id for the indirect target. Present only when FunctionKind is 2. | | ||
+---------------------+-----------------------------------------------------------------------+ | ||
| CallSiteCount | Number of type id to indirect call site mappings that follow. | | ||
+---------------------+-----------------------------------------------------------------------+ | ||
| CallSiteList | List of type id and indirect call site pc pairs. | | ||
+---------------------+-----------------------------------------------------------------------+ | ||
|
||
Each element in an entry (including each element of the contained lists and | ||
pairs) occupies 64-bit space. | ||
|
||
The format version number is repeated per entry to support concatenation of | ||
call graph sections with different format versions by the linker. | ||
|
||
As of now, the only supported format version is described above and has version | ||
number 0. | ||
|
||
Type identifiers | ||
================ | ||
|
||
The type for an indirect call or target is the function signature. | ||
The mapping from a type to an identifier is an ABI detail. | ||
In the current experimental implementation, an identifier of type T is | ||
computed as follows: | ||
|
||
- Obtain the generalized mangled name for “typeinfo name for T”. | ||
- Compute MD5 hash of the name as a string. | ||
- Reinterpret the first 8 bytes of the hash as a little-endian 64-bit integer. | ||
|
||
To avoid mismatched pointer types, generalizations are applied. | ||
Pointers in return and argument types are treated as equivalent as long as the | ||
qualifiers for the type they point to match. | ||
For example, ``char*``, ``char**``, and ``int*`` are considered equivalent | ||
types. However, ``char*`` and ``const char*`` are considered separate types. | ||
Prabhuk marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
Missing type identifiers | ||
======================== | ||
|
||
For functions, two cases need to be considered. First, if the compiler cannot | ||
deduce a type id for an indirect target, it will be listed as an indirect target | ||
without a type id. Second, if an object without a call graph section gets | ||
linked, the final call graph section will lack information on functions from | ||
the object. For completeness, these functions need to be taken as receiver to | ||
any indirect call regardless of their type id. | ||
``llvm-objdump --call-graph-info`` lists these functions as indirect targets | ||
with `UNKNOWN` type id. | ||
|
||
For indirect calls, current implementation guarantees a type id for each | ||
compiled call. However, if an object without a call graph section gets linked, | ||
no type id will be present for its indirect calls. For completeness, these calls | ||
need to be taken to target any indirect target regardless of their type id. For | ||
indirect calls, ``llvm-objdump --call-graph-info`` prints 1) a complete list of | ||
indirect calls, 2) type id to indirect call mappings. The difference of these | ||
lists allow to deduce the indirect calls with missing type ids. | ||
|
||
TODO: measure and report the ratio of missed type ids | ||
|
||
Performance | ||
=========== | ||
|
||
A call graph section does not affect the executable code and does not occupy | ||
memory during process execution. Therefore, there is no performance overhead. | ||
|
||
The scheme has not yet been optimized for binary size. | ||
|
||
TODO: measure and report the increase in the binary size | ||
|
||
Example | ||
======= | ||
|
||
For example, consider the following C++ code: | ||
|
||
.. code-block:: cpp | ||
namespace { | ||
// Not an indirect target | ||
void foo() {} | ||
} | ||
// Indirect target 1 | ||
void bar() {} | ||
// Indirect target 2 | ||
int baz(char a, float *b) { | ||
return 0; | ||
} | ||
// Indirect target 3 | ||
int main() { | ||
char a; | ||
float b; | ||
void (*fp_bar)() = bar; | ||
int (*fp_baz1)(char, float*) = baz; | ||
int (*fp_baz2)(char, float*) = baz; | ||
// Indirect call site 1 | ||
fp_bar(); | ||
// Indirect call site 2 | ||
fp_baz1(a, &b); | ||
// Indirect call site 3: shares the type id with indirect call site 2 | ||
fp_baz2(a, &b); | ||
// Direct call sites | ||
foo(); | ||
bar(); | ||
baz(a, &b); | ||
return 0; | ||
} | ||
Following will compile it with a call graph section created in the binary: | ||
|
||
.. code-block:: bash | ||
$ clang -fcall-graph-section example.cpp | ||
During the construction of the call graph section, the type identifiers are | ||
computed as follows: | ||
|
||
+---------------+-----------------------+----------------------------+----------------------------+ | ||
| Function name | Generalized signature | Mangled name (itanium ABI) | Numeric type id (md5 hash) | | ||
+===============+=======================+============================+============================+ | ||
| bar | void () | _ZTSFvvE.generalized | f85c699bb8ef20a2 | | ||
+---------------+-----------------------+----------------------------+----------------------------+ | ||
| baz | int (char, void*) | _ZTSFicPvE.generalized | e3804d2a7f2b03fe | | ||
+---------------+-----------------------+----------------------------+----------------------------+ | ||
| main | int () | _ZTSFivE.generalized | a9494def81a01dc | | ||
+---------------+-----------------------+----------------------------+----------------------------+ | ||
|
||
The call graph section will have the following content: | ||
|
||
+---------------+-----------------+--------------+----------------+---------------+--------------------------------------+ | ||
| FormatVersion | FunctionEntryPc | FunctionKind | FunctionTypeId | CallSiteCount | CallSiteList | | ||
+===============+=================+==============+================+===============+======================================+ | ||
| 0 | EntryPc(foo) | 0 | (empty) | 0 | (empty) | | ||
+---------------+-----------------+--------------+----------------+---------------+--------------------------------------+ | ||
| 0 | EntryPc(bar) | 2 | TypeId(bar) | 0 | (empty) | | ||
+---------------+-----------------+--------------+----------------+---------------+--------------------------------------+ | ||
| 0 | EntryPc(baz) | 2 | TypeId(baz) | 0 | (empty) | | ||
+---------------+-----------------+--------------+----------------+---------------+--------------------------------------+ | ||
| 0 | EntryPc(main) | 2 | TypeId(main) | 3 | * TypeId(bar), CallSitePc(fp_bar()) | | ||
| | | | | | * TypeId(baz), CallSitePc(fp_baz1()) | | ||
| | | | | | * TypeId(baz), CallSitePc(fp_baz2()) | | ||
+---------------+-----------------+--------------+----------------+---------------+--------------------------------------+ | ||
|
||
|
||
The ``llvm-objdump`` utility can parse the call graph section and disassemble | ||
the program to provide complete call graph information. This includes any | ||
additional call sites from the binary: | ||
|
||
.. code-block:: bash | ||
$ llvm-objdump --call-graph-info a.out | ||
# Comments are not a part of the llvm-objdump's output but inserted for clarifications. | ||
a.out: file format elf64-x86-64 | ||
# These warnings are due to the functions and the indirect calls coming from linked objects. | ||
llvm-objdump: warning: 'a.out': callgraph section does not have type ids for 3 indirect calls | ||
llvm-objdump: warning: 'a.out': callgraph section does not have information for 10 functions | ||
# Unknown targets are the 10 functions the warnings mention. | ||
INDIRECT TARGET TYPES (TYPEID [FUNC_ADDR,]) | ||
UNKNOWN 401000 401100 401234 401050 401090 4010d0 4011d0 401020 401060 401230 | ||
a9494def81a01dc 401150 # main() | ||
f85c699bb8ef20a2 401120 # bar() | ||
e3804d2a7f2b03fe 401130 # baz() | ||
# Notice that the call sites share the same type id as target functions | ||
INDIRECT CALL TYPES (TYPEID [CALL_SITE_ADDR,]) | ||
f85c699bb8ef20a2 401181 # Indirect call site 1 (fp_bar()) | ||
e3804d2a7f2b03fe 401191 4011a1 # Indirect call site 2 and 3 (fp_baz1() and fp_baz2()) | ||
INDIRECT CALL SITES (CALLER_ADDR [CALL_SITE_ADDR,]) | ||
401000 401012 # _init | ||
401150 401181 401191 4011a1 # main calls fp_bar(), fp_baz1(), fp_baz2() | ||
4011d0 401215 # __libc_csu_init | ||
401020 40104a # _start | ||
DIRECT CALL SITES (CALLER_ADDR [(CALL_SITE_ADDR, TARGET_ADDR),]) | ||
4010d0 4010e2 401060 # __do_global_dtors_aux | ||
401150 4011a6 401110 4011ab 401120 4011ba 401130 # main calls foo(), bar(), baz() | ||
4011d0 4011fd 401000 # __libc_csu_init | ||
FUNCTIONS (FUNC_ENTRY_ADDR, SYM_NAME) | ||
401000 _init | ||
401100 frame_dummy | ||
401234 _fini | ||
401050 _dl_relocate_static_pie | ||
401090 register_tm_clones | ||
4010d0 __do_global_dtors_aux | ||
401110 _ZN12_GLOBAL__N_13fooEv # (anonymous namespace)::foo() | ||
401150 main # main | ||
4011d0 __libc_csu_init | ||
401020 _start | ||
401060 deregister_tm_clones | ||
401120 _Z3barv # bar() | ||
401130 _Z3bazcPf # baz(char, float*) | ||
401230 __libc_csu_fini |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -455,6 +455,7 @@ static bool initTargetOptions(DiagnosticsEngine &Diags, | |
Options.StackUsageOutput = CodeGenOpts.StackUsageOutput; | ||
Options.EmitAddrsig = CodeGenOpts.Addrsig; | ||
Options.ForceDwarfFrameSection = CodeGenOpts.ForceDwarfFrameSection; | ||
Options.EmitCallGraphSection = CodeGenOpts.CallGraphSection; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. TargetOptions :( |
||
Options.EmitCallSiteInfo = CodeGenOpts.EmitCallSiteInfo; | ||
Options.EnableAIXExtendedAltivecABI = LangOpts.EnableAIXExtendedAltivecABI; | ||
Options.XRayFunctionIndex = CodeGenOpts.XRayFunctionIndex; | ||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.