Draft: Add CaGe LLVM call graph generator #82
Conversation
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
sebastiankreutzer
force-pushed
the
feat/cage
branch
7 times, most recently
from
ca75a03 to
dae1168
Compare
Merged
Co-authored-by: Tim Heldmann <tim.heldmann@tu-darmstadt.de> # Conflicts: # tools/CMakeLists.txt
sebastiankreutzer
force-pushed
the
feat/cage
branch
from
dae1168 to
364ef42
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This patch adds CaGe, the call graph generator plugin for LLVM developed by @TimHeldmann.
This version is slightly modified from the original project to fit in with the rest of the MetaCG project.
So far, this patch only contains functionality to register the pass and build the call graph.
It does not include any call graph embedding functionality or runtime library for now.
To make this project easily extendable for different use cases, the pass can register different
CallGraphCosumers.At the moment, the only available consumer is the
FileExporter, which writes the call graph to a file.This is still a draft, as there is more work to be done to support proper testing.
Note: This patch relies on #83 and will be rebased on
develwhen it is accepted.