ystem headers (e.g., the host libstdc++)
Likewise.
3. it outputs a summary (which can be used for building graphs, like
you do for benchmarks)
Yep, written to my TODO list.
Please be aware that we have some connection issues with gcc.opensuse.org, but
updated LCOV will appear there soon.
T
;>>>
>>>> I've been working on some patches for GCOV and lcov was of my test
>>>> scenarios.
>>>> I'm sending link to static HTML pages made by the tool which are
>>>> recorded
>>>> for GCC (w/o bootstrap) build + runn
On 04/28/2017 06:53 PM, David Malcolm wrote:
> On Fri, 2017-04-28 at 11:38 +0200, Richard Biener wrote:
>> On Fri, Apr 28, 2017 at 11:07 AM, Martin Liška
>> wrote:
>>> Hello.
>>>
>>> I've been working on some patches for GCOV and lcov was of my tes
On Fri, 28 Apr 2017, Jeff Law wrote:
> I did some similar work a few years back. Martin's results are comparable to
> mine. Interestingly enough the 70-80% coverage we see for GCC is a "sweet
> spot" in that several of the ancillary tools I tested were in the same overall
> range.
My observat
On Fri, 2017-04-28 at 11:38 +0200, Richard Biener wrote:
> On Fri, Apr 28, 2017 at 11:07 AM, Martin Liška
> wrote:
> > Hello.
> >
> > I've been working on some patches for GCOV and lcov was of my test
> > scenarios.
> > I'm sending link t
On 04/28/2017 03:38 AM, Richard Biener wrote:
On Fri, Apr 28, 2017 at 11:07 AM, Martin Liška wrote:
Hello.
I've been working on some patches for GCOV and lcov was of my test scenarios.
I'm sending link to static HTML pages made by the tool which are recorded
for GCC (w/o bootst
On Fri, Apr 28, 2017 at 11:07 AM, Martin Liška wrote:
> Hello.
>
> I've been working on some patches for GCOV and lcov was of my test scenarios.
> I'm sending link to static HTML pages made by the tool which are recorded
> for GCC (w/o bootstrap) build + running test-
Hello.
I've been working on some patches for GCOV and lcov was of my test scenarios.
I'm sending link to static HTML pages made by the tool which are recorded
for GCC (w/o bootstrap) build + running test-suite on x86_64-linux-gnu.
I'm planning to set up a periodic build of
TK Banks writes:
> Would it be poor-form to submit a bug without first testing on the latest
> version of the compiler? (I'm just running whatever version Ubuntu doles out
> via the management system: 4.3.4)
It's OK to do that, just make clear that version of the compiler you
tested.
Ian
From: Ian Lance Taylor
To: TK Banks
Cc: "gcc@gcc.gnu.org"
Sent: Tuesday, May 29, 2012 4:27 PM
Subject: Re: gcov / lcov producing icorrect results due to white space in
source.
TK Banks writes:
> I'm also not sure I'm directing this issue to the correct mailing list.
>
cc-h...@gcc.gnu.org. Please take any followups there.
Thanks.
> I am a member of a perhaps dying breed that likes opening and closing braces
> to line up vertically. This is causing lcov & gcov
> to incorrectly claim that the line associated with the opening
> brace of some cons
tu 4.4.3-4ubuntu5.1) 4.4.3
> lcov --version
lcov: LCOV version 1.7
THE PROBLEM:
I am a member of a perhaps dying breed that likes opening and closing braces to
line up vertically. This is causing lcov & gcov
to incorrectly claim that the line associated with the opening
brace of some const
Original Message
>From: Dickson Patton
>Sent: 27 June 2005 18:41
> All,
>
> LCOV looks like what we were planning. Let's steal it.
>
> See you at 7:00.
>
>
> Dickson
Sorry, I couldn't make it. Did you save any beer for me?
cheers
All,
LCOV looks like what we were planning. Let's steal it.
See you at 7:00.
Dickson
14 matches
Mail list logo
