[llvm-testresults] buildbot failure in llvm on llvm-gcc-i386-linux-selfhost
jan_sjodin at yahoo.com
Sat Mar 12 07:17:10 CST 2011
Since my code does change the way the debug info is emitted it is likely to be
my change, but i would have expected it to fail in stage 1 in that case. It is
strange that slightly different debug info should cause a miscompile.
From: Duncan Sands <baldrick at free.fr>
To: NAKAMURA Takumi <geek4civic at gmail.com>
Cc: llvm-testresults <llvm-testresults at cs.uiuc.edu>; Daniel Dunbar
<daniel at zuster.org>; Jan Sjodin <jan_sjodin at yahoo.com>; Peter Collingbourne
<peter at pcc.me.uk>
Sent: Sat, March 12, 2011 7:43:03 AM
Subject: Re: [llvm-testresults] buildbot failure in llvm on
On 12/03/11 12:11, NAKAMURA Takumi wrote:
> It seems it has been failing on since then. Why?
The llvm-x86_64-linux-checks builder is failing in the same way: these tests
are failing in stage2:
They do not fail in stage 1, suggesting a miscompile. The first failures were
The set of commits for the llvm-x86_64-linux-checks builder is a strict superset
of those implicated by the llvm-gcc-i386-linux-selfhost builder. Eliminating
those involving clang, this leaves two commits. I think the first one, by
ddunbar, can be eliminated: it was reverting a recent change, so is unlikely
to have introduced a miscompilation, and the original patch has since been
reapplied without fixing the buildbots. So that leaves jsjodin's change which
I am about to try reverting.
Changed by: ddunbar
Changed at: Fri 11 Mar 2011 11:35:18
Revert r127459, "Optimize trivial branches in CodeGenPrepare, which often get
created from the", it broke some GCC test suite tests.
Changed by: jsjodin
Changed at: Fri 11 Mar 2011 11:41:18
Remove optimization emitting a reference insted of label difference, since it
can create more relocations. Removed isBaseAddressKnownZero method, because it
is no longer used.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-testresults