Thanks Ian.
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)


Yeah, I noticed that my lines got joined.  It looked good in my yahoo mailer 
text box before I hit send.  Most annoying.  I'm guessing it had something to 
do with the fact that it was cut-n-paste from a web page generated by a 
unix-based web server and into a windows-based web-mailer.  I'll blame it on 
yahoo.


Thanks again,
Matt Busche






----- Original Message -----
From: Ian Lance Taylor <i...@google.com>
To: TK Banks <spammymat...@yahoo.com>
Cc: "gcc@gcc.gnu.org" <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 <spammymat...@yahoo.com> writes:

> I'm also not sure I'm directing this issue to the correct mailing list.
> If not, perhaps someone would be so kind as to point me to the right
> mailing list or forum.

In fact, gcc@gcc.gnu.org is the wrong mailing list.  The right mailing
list would be gcc-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 constructors to never be hit by my unit tests.  Here
> is a sample snip-it of lcov output for one of my constructors:
>
> 1135  :     template<typename M, typename V> 1136 14 :     inline 
> Group<M,V>::Group(Domain<M,V>& d) 1137  :         :   _domain(&d), 1138  :    
>          _end(this, &_end, &_end, 0x80000000), 1139 14 :             _size(0) 
> 1140 0 :     { 1141 14 :     }
>
> Notice that line 1140 is said to be executed zero times.  In my
> browser, it's highlighted in an obnoxious and most chastising red.

I can't figure out your line breaks there--all the code is on a single
line.  That said, it sounds like this is a small bug somewhere, and I
would guess it is somewhere in GCC.  Please report it following the
instructions at http://gcc.gnu.org/bugs/ .  Thanks.

Ian

Reply via email to