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

[Marc-André Laperle via llvm-dev]

"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."


A tool like Trace Compass could help here, it does scale pretty well. (see tracecompass.org<http://tracecompass.org/>)

I'm replying here so a colleague who just suscribed to the mailing list can reply here.


Marc-André


________________________________
From: cfe-dev <cfe-dev-bounces at lists.llvm.org> on behalf of Dean Michael Berris via cfe-dev <cfe-dev at lists.llvm.org>
Sent: Tuesday, December 5, 2017 3:52 PM
To: Brian Cain
Cc: LLVM Developers; Keith Wyss; Clang Dev
Subject: Re: [cfe-dev] XRay Trace of Clang, Loadable through Chrome Trace Viewer



Sent from my iPhone

On 6 Dec 2017, at 4:17 am, Brian Cain <brian.cain at gmail.com<mailto: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<mailto: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/63360940/attachment.html>