Compiler Static Information Integration#272
Open
Yejashi wants to merge 9 commits intollnl:developfrom
Open
Conversation
afac521 to cb4d3c9 Compare 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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 PR introduces support for integrating statically collected compiler information into Thicket. The feature enables users to correlate Thicket performance analysis with LLVM IR statistics, optimization remark statistics, and backend kernel resource usage (KRU) collected through LLVM pass plugins.
The implementation links static compiler analysis with runtime Caliper regions using a trace mapping generated during execution.
This integration allows users to analyze compiler behavior alongside runtime performance metrics within the same Thicket data structure.