<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
(Sorry for the divergence)</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi Amy,</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="margin:0px;font-size:15px;font-family:"Segoe UI", "Segoe UI Web (West European)", "Segoe UI", -apple-system, BlinkMacSystemFont, Roboto, "Helvetica Neue", sans-serif;color:rgb(32, 31, 30);background-color:rgb(255, 255, 255)">>Unfortunately running
llvm-locstats fails on the chrome binary, so no coverage stats.</span><br>
</div>
<div style=""><font color="#201f1e"><span style="font-size: 15px;">Can you please file a bug against this, so we can take a look? I am wondering if the problem is on the llvm-locstats or on the llvm-dwarfdump --statistics side.</span></font></div>
<div style=""><font color="#201f1e"><span style="font-size: 15px;"><br>
</span></font></div>
<div style=""><font color="#201f1e"><span style="font-size: 15px;">Best,</span></font></div>
<div style=""><font color="#201f1e"><span style="font-size: 15px;">Djordje</span></font></div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Jeremy Morse <jeremy.morse.llvm@gmail.com><br>
<b>Sent:</b> Wednesday, August 18, 2021 10:30 PM<br>
<b>To:</b> Amy Huang <akhuang@google.com><br>
<b>Cc:</b> llvm-dev <llvm-dev@lists.llvm.org>; Adrian Prantl <aprantl@apple.com>; Paul Robinson <paul.robinson@sony.com>; Eric Christopher <echristo@gmail.com>; Jonas Devlieghere <jdevlieghere@apple.com>; David Blaikie <dblaikie@gmail.com>; Reid Kleckner <rnk@google.com>;
Vedant Kumar <vsk@apple.com>; Djordje Todorovic <Djordje.Todorovic@syrmia.com>; Cazalet-Hyams, Orlando <orlando.hyams@sony.com>; Tozer, Stephen <Stephen.Tozer@sony.com><br>
<b>Subject:</b> Re: [llvm-dev] Call for testing -- new variable location tracking solution</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hi Amy,<br>
<br>
On Wed, Aug 18, 2021 at 8:58 PM Amy Huang <akhuang@google.com> wrote:<br>
> Just wanted to say I've tried building Chrome with this (with -g2 -O2) on Linux and didn't see a noticeable difference in compile time.<br>
<br>
Excellent, that's really reassuring given how large chrome is, thanks<br>
for trying a build with the flag,<br>
<br>
> Unfortunately running llvm-locstats fails on the chrome binary, so no coverage stats.<br>
<br>
That's a shame; however I'm confident there won't be a coverage<br>
regression, detecting any performance cliff edges was my main aim<br>
here.<br>
<br>
--<br>
Thanks,<br>
Jeremy<br>
</div>
</span></font></div>
</body>
</html>