daniel at zuster.org
Mon Feb 15 18:46:52 PST 2010
On Mon, Feb 15, 2010 at 1:22 PM, David Greene <dag at cray.com> wrote:
> On Monday 15 February 2010 12:16:21 Daniel Dunbar wrote:
>> No, some build release, and some build release-asserts.
>> Historically, this is a typical sign of llvm being miscompiled, see
>> the broken-gcc list.
> Yep, that's it. We've been happily using gcc 4.1.2 on OpenSUSE for test
> builds for some time without problem (we don't use it for releases yet, and
> won't now!). I guess something changed to make the issue visible to us.
> BTW, how sure are we that all these are gcc issues and not some incorrect
> code somewhere that triggers undefined behavior?
Medium sure? :)
I spent a little while hunting this particular bug, and it acted very
much like a compiler bug. I never narrowed it down to a test case,
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
More information about the llvm-dev