[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Patchy email
From: |
Graham Percival |
Subject: |
Re: Patchy email |
Date: |
Wed, 4 Jan 2012 00:48:49 -0800 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Wed, Jan 04, 2012 at 09:38:57AM +0100, David Kastrup wrote:
> address@hidden writes:
> > nice make doc -j3 CPU_COUNT=3
> >
> > Previous good commit: 2fd5a378f5d883536b1aac57583d261ce60a4043
> >
> > Current broken commit: c1a1f9684b6cfab2e4b4d813db6058c7d22b9b0a
>
> My guess would be on
>
> commit 9f24e79a945ec4ab000d3e09ff2d2ac8208e2246
> since c1a1f9684b6cfab2e4b4d813db6058c7d22b9b0a is just a rewording and
> quite trivial.
Apparently a later build succeeded. Either something's weird in
Patchy, or it's yet another instance of some uninitialized
variable or memory. Since there isn't much interest in cleaning
up compiler warnings[1] so that we can use automatic tools to
identify such problematic occurrences, I guess we'll just stumble
forward as usual.
[1] if your version of g++ doesn't find a ton of warnings -- on
any architecture -- try using clang 3.0.
Cheers,
- Graham
- Re: Patchy email, David Kastrup, 2012/01/01
- Patchy email, lilypond . patchy . graham, 2012/01/06
- Patchy email, lilypond . patchy . graham, 2012/01/06
- Patchy email, lilypond . patchy . graham, 2012/01/09
- Patchy email, lilypond . patchy . graham, 2012/01/09