forked from OSchip/llvm-project
424279958d
Minimal tool to convert xray traces to Chrome's Trace Event Format. Summary: Make use of Chrome Trace Event format's Duration events and stack frame dict to produce Json files that chrome://tracing can visualize from xray function call traces. Trace Event format is more robust and has several features like argument logging, function categorization, multi process traces, etc. that we can add as needed. Duration events cover an important base case. Part of this change is rearranging the code so that the TrieNode data structure can be used from multiple tools and can carry parameterized baggage on the nodes. I put the actual behavior changes in llvm-xray convert exclusively. Exploring the trace of instrumented llc was pretty nifty if overwhelming. I can envision this being very useful for analyzing contention scenarios or tuning parameters like batch sizes in a producer consumer queue. For more targeted traces likemthis, let's talk about how we want to approach trace pruning. Reviewers: dberris, pelikan Subscribers: llvm-commits Differential Revision: https://reviews.llvm.org/D39362 llvm-svn: 317531 |
||
---|---|---|
.. | ||
CMakeLists.txt | ||
func-id-helper.cc | ||
func-id-helper.h | ||
llvm-xray.cc | ||
trie-node.h | ||
xray-account.cc | ||
xray-account.h | ||
xray-color-helper.cc | ||
xray-color-helper.h | ||
xray-converter.cc | ||
xray-converter.h | ||
xray-extract.cc | ||
xray-graph-diff.cc | ||
xray-graph-diff.h | ||
xray-graph.cc | ||
xray-graph.h | ||
xray-record-yaml.h | ||
xray-registry.cc | ||
xray-registry.h | ||
xray-stacks.cc |