[llvm-dev] [cfe-dev] XRay Trace of Clang, Loadable through Chrome Trace Viewer

Dean Michael Berris via llvm-dev llvm-dev at lists.llvm.org
Tue Dec 5 12:52:58 PST 2017



Sent from my iPhone

> On 6 Dec 2017, at 4:17 am, Brian Cain <brian.cain at gmail.com> wrote:
> 
> 
> 
>> On Tue, Dec 5, 2017 at 9:49 AM, Dean Michael Berris via cfe-dev <cfe-dev at lists.llvm.org> wrote:
>> Hi cfe-dev@ and llvm-dev@,
>> 
>> I've attached a Chrome trace-viewer readable trace of a clang built with XRay instrumentation (additional build/link flags="-fxray-instrument -fxray-instruction-threshold=75") with the latest "top-of-trunk" version of clang with the recent updates to the XRay runtime supporting record filtering.
>> 
>> To load the attached file, go to 'chrome://tracing' in your Chrome/Chromium browser and load the .gz file directly. Pressing '?' should give a help dialog.
>> 
> 
> 
> This is an interesting feature.  Is it designed to accept arbitrary xray trace logs or only ones for/from Chrome/ium?
> 

Yes, it works on any XRay trace generated with the logging implementations that come with XRay in compiler-rt.

The example attached was of an instrumented Clang binary compiling C++ code. 😁

The caveat is, while the tool (llvm-xray convert) can generate arbitrarily large Chrome-loadable traces, the Chrome trace viewer can only handle so much data.

Cheers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20171206/42ffb362/attachment.html>


More information about the llvm-dev mailing list