<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Sweet stuff! Thanks for sharing this, Marc-André!<div class=""><br class=""></div><div class="">It seems like Trace Compass can already handle CTF. I suspect if we implemented a converter to CTF, that we can turn XRay traces into something that can be visualised with this. That, or have Trace Compass load XRay traces natively.</div><div class=""><br class=""></div><div class="">Cheers</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 7 Dec 2017, at 03:47, Marc-André Laperle <<a href="mailto:marc-andre.laperle@ericsson.com" class="">marc-andre.laperle@ericsson.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div id="divtagdefaultwrapper" dir="ltr" style="font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; font-size: 12pt; font-family: Calibri, Helvetica, sans-serif, EmojiFont, 'Apple Color Emoji', 'Segoe UI Emoji', NotoColorEmoji, 'Segoe UI Symbol', 'Android Emoji', EmojiSymbols;" class=""><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class="">"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."</span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class=""><br class=""></span></div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><span class="">A tool like Trace Compass could help here, it does scale pretty well. (see<span class="Apple-converted-space"> </span></span><a href="http://tracecompass.org/" class="OWAAutoLink" id="LPlnk938183" previewremoved="true"><span class=""></span>tracecompass.org</a>)</div><div style="margin-top: 0px; margin-bottom: 0px;" class="">I'm replying here so a colleague who just suscribed to the mailing list can reply here.</div><div style="margin-top: 0px; margin-bottom: 0px;" class=""><br class=""></div><div style="margin-top: 0px; margin-bottom: 0px;" class="">Marc-André<br class=""></div><br class=""><br class=""><div style="" class=""><hr tabindex="-1" style="display: inline-block; width: 1129.9375px;" class=""><div id="divRplyFwdMsg" dir="ltr" class=""><font face="Calibri, sans-serif" style="font-size: 11pt;" class=""><b class="">From:</b><span class="Apple-converted-space"> </span>cfe-dev <<a href="mailto:cfe-dev-bounces@lists.llvm.org" class="">cfe-dev-bounces@lists.llvm.org</a>> on behalf of Dean Michael Berris via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a>><br class=""><b class="">Sent:</b><span class="Apple-converted-space"> </span>Tuesday, December 5, 2017 3:52 PM<br class=""><b class="">To:</b><span class="Apple-converted-space"> </span>Brian Cain<br class=""><b class="">Cc:</b><span class="Apple-converted-space"> </span>LLVM Developers; Keith Wyss; Clang Dev<br class=""><b class="">Subject:</b><span class="Apple-converted-space"> </span>Re: [cfe-dev] XRay Trace of Clang, Loadable through Chrome Trace Viewer</font><div class=""> </div></div><div dir="auto" class=""><br class=""><br class=""><div id="x_AppleMailSignature" class="">Sent from my iPhone</div><div class=""><br class="">On 6 Dec 2017, at 4:17 am, Brian Cain <<a href="mailto:brian.cain@gmail.com" class="">brian.cain@gmail.com</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><br class=""><div class="x_gmail_extra"><br class=""><div class="x_gmail_quote">On Tue, Dec 5, 2017 at 9:49 AM, Dean Michael Berris via cfe-dev<span class="Apple-converted-space"> </span><span dir="ltr" class=""><<a href="mailto:cfe-dev@lists.llvm.org" target="_blank" class="">cfe-dev@lists.llvm.org</a>></span><span class="Apple-converted-space"> </span>wrote:<br class=""><blockquote class="x_gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;">Hi cfe-dev@ and llvm-dev@,<br class=""><br class="">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=<wbr class="">75") with the latest "top-of-trunk" version of clang with the recent updates to the XRay runtime supporting record filtering.<br class=""><br class="">To load the attached file, go to '<a href="chrome://tracing" class="">chrome://tracing</a>' in your Chrome/Chromium browser and load the .gz file directly. Pressing '?' should give a help dialog.<br class=""><br class=""></blockquote><div class=""><br class=""></div><div class=""><br class=""></div><div class="">This is an interesting feature. Is it designed to accept arbitrary xray trace logs or only ones for/from Chrome/ium?</div><div class=""><br class=""></div></div></div></div></div></blockquote><div class=""><br class=""></div>Yes, it works on any XRay trace generated with the logging implementations that come with XRay in compiler-rt.<div class=""><br class=""></div><div class="">The example attached was of an instrumented Clang binary compiling C++ code. 😁</div><div class=""><br class=""></div><div class="">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.</div><div class=""><br class=""></div><div class="">Cheers</div></div></div></div></div></blockquote></div><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">-- Dean</div></div>
</div>
<br class=""></div></body></html>