(original) (raw)
(Sorry for the divergence)
Hi Amy,
>Unfortunately running
llvm-locstats fails on the chrome binary, so no coverage stats.
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.
Best,
Djordje
From: Jeremy Morse
Sent: Wednesday, August 18, 2021 10:30 PM
To: Amy Huang
Cc: llvm-dev ; Adrian Prantl ; Paul Robinson ; Eric Christopher ; Jonas Devlieghere ; David Blaikie ; Reid Kleckner ; Vedant Kumar ; Djordje Todorovic ; Cazalet-Hyams, Orlando ; Tozer, Stephen
Subject: Re: \[llvm-dev\] Call for testing -- new variable location tracking solution
Sent: Wednesday, August 18, 2021 10:30 PM
To: Amy Huang
Cc: llvm-dev ; Adrian Prantl ; Paul Robinson ; Eric Christopher ; Jonas Devlieghere ; David Blaikie ; Reid Kleckner ; Vedant Kumar ; Djordje Todorovic ; Cazalet-Hyams, Orlando ; Tozer, Stephen
Subject: Re: \[llvm-dev\] Call for testing -- new variable location tracking solution
Hi Amy,
On Wed, Aug 18, 2021 at 8:58 PM Amy Huang wrote:
\> 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.
Excellent, that's really reassuring given how large chrome is, thanks
for trying a build with the flag,
\> Unfortunately running llvm-locstats fails on the chrome binary, so no coverage stats.
That's a shame; however I'm confident there won't be a coverage
regression, detecting any performance cliff edges was my main aim
here.
\--
Thanks,
Jeremy
On Wed, Aug 18, 2021 at 8:58 PM Amy Huang wrote:
\> 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.
Excellent, that's really reassuring given how large chrome is, thanks
for trying a build with the flag,
\> Unfortunately running llvm-locstats fails on the chrome binary, so no coverage stats.
That's a shame; however I'm confident there won't be a coverage
regression, detecting any performance cliff edges was my main aim
here.
\--
Thanks,
Jeremy