[llvm-testresults] Broken buildbot: llvm-gcc-i386-linux-selfhost

Jakob Stoklund Olesen stoklund at 2pi.dk
Fri Sep 24 11:14:06 PDT 2010


On Sep 24, 2010, at 11:05 AM, Rafael Espindola wrote:

>> I didn't notice before, but the failures contain stack dumps. It looks like llvm-mc is crashing on those tests, but only the stage2 llvm-mc.
>> 
>> It is our only self-hosting i386-linux tester.
>> 
>> Rafael, is the ELF writer used when running llvm-mc on Linux? That might explain why it is only failing on Linux.
> 
> Only if you pass --filetype=obj, which is not the default. You
> mentioned FileCheck being miscompiled, so that is why I think that is
> probably no the patch that broke it.

I think I was wrong. I missed the stack traces.

It looks like llvm-mc is crashing, producing a stack trace and truncated output.

FileCheck is then complaining because the truncated output doesn't match. This caused weird error messages that I though looked like a miscompiled FileCheck.

Note that many tests are passing -filetype=obj to llvm-mc, but none of them are failing in this bot.

I suspect we are looking at a miscompilation of llvm-mc, or undefined behaviour in llvm-mc that LLVM exposes more than GCC did.

/jakob





More information about the llvm-testresults mailing list