[PATCH] D39362: [XRay] Minimal tool to convert xray traces to Chrome's Trace Event Format.

[Keith via Phabricator via llvm-commits]

kpw created this revision.

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.


https://reviews.llvm.org/D39362

Files:
  tools/llvm-xray/stack-trie.h
  tools/llvm-xray/xray-converter.cc
  tools/llvm-xray/xray-converter.h
  tools/llvm-xray/xray-stacks.cc

-------------- next part --------------
A non-text attachment was scrubbed...
Name: D39362.120544.patch
Type: text/x-patch
Size: 30437 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20171027/d299bc3f/attachment.bin>