Joe Buck wrote:
> On Wed, Jun 06, 2007 at 11:13:16AM -0700, Lothar Werzinger wrote:
>> when I build a coverage build of my software I get some undefined symbols
>> like global constructors keyed to src_utility_Tree.cpp_90B986A5_564B8955
>>
>> I did some investigatio
Hi,
when I build a coverage build of my software I get some undefined symbols
like global constructors keyed to src_utility_Tree.cpp_90B986A5_564B8955
I did some investigation and as you can see in the below test it only occurs
if I specify -Woverloaded-virtual.
What is strange, too is that if I
Andreas Schwab wrote:
> 1 && 0 is still 0.
>
> Andreas.
Oops my bad. Didn't think (long enough) before posting ;-)
Lothar
Eyal Lebedinsky wrote:
> I see two kinds of warnings:
> warning: logical '||' with non-zero constant will always evaluate as true
> warning: logical '&&' with non-zero constant will always evaluate as true
>
> The first statement is true, the second false. It can say (if the case is
> such) warni
balazs wrote:
> Hi - I start a simple pthread and the program consumes about 10 Mbytes of
> virtual memory. If I start 10 threads, it consumes 100 Mbytes.
That's off topic, but the answer is that the default stack size for a thread
on your machine seems to be 10M. If you know you don't need such
Did anybody do some metrics how big the savings would be?
I think we should loom at the metrics before jumping to
conclusions about implementing such a feature.
I have strange ICEs (that come and go as I rearrange the source - like the
sequence of include statements). They appear also to affect different files
on different machines we compile on.
This one here seems to go away if I remove -fprofile-arcs -ftest-coverage
from the commandline.
It would be gr
