The buildbots are unhappy again. :-( Specifically, the "llvm-gcc-i386-darwin9" buildbot here at Apple last compiled TOT successfully yesterday morning (31aug); that was revision 80586. By revision 80589, the bootstrap failed due to a miscompare, and by revision 80610, it's aborting while compiling little pieces of libgcc. 80586 built O.K. (about 8AM, Pacific Standard Time, on Monday 31aug) ... 80589 bootstrap miscompare (about one hour after 80586) ... 80610 abort()s while compiling libgcc (about two hours after 80589) ... 80717 (current as I write this, on Tuesday 01sep) still broken I realize that everyone is busy, but I think TOT has been broken long enough. Would everyone that committed any patches yesterday please check your work with a clean make of TOT? Thank you in advance, stuart
Yes, this is pretty unacceptable IMHO. I would go revert crazy if I knew what to hit, unfortunately I don't. Currently I believe there are two problems, a CallGraphSCC assert which is firing everywhere (including the clang test suite, *cough*). This started with 80698. Chris is working on this (if it isn't already fixed). The bootstrap comparison failures are being looked at by Devang. - Daniel On Tue, Sep 1, 2009 at 1:54 PM, Stuart Hastings<stuart at apple.com> wrote:> The buildbots are unhappy again. :-( > > Specifically, the "llvm-gcc-i386-darwin9" buildbot here at Apple last > compiled TOT successfully yesterday morning (31aug); that was revision > 80586. By revision 80589, the bootstrap failed due to a miscompare, > and by revision 80610, it's aborting while compiling little pieces of > libgcc. > > 80586 built O.K. (about 8AM, Pacific Standard Time, on Monday 31aug) > ... > 80589 bootstrap miscompare (about one hour after 80586) > ... > 80610 abort()s while compiling libgcc (about two hours after 80589) > ... > 80717 (current as I write this, on Tuesday 01sep) still broken > > I realize that everyone is busy, but I think TOT has been broken long > enough. Would everyone that committed any patches yesterday please > check your work with a clean make of TOT? > > Thank you in advance, > > stuart > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
For those not seeing the failures on the Google build bots. That's because they're not building llvm-gcc with bootstrap (or, indeed, at all). -bw On Tue, Sep 1, 2009 at 1:54 PM, Stuart Hastings<stuart at apple.com> wrote:> The buildbots are unhappy again. :-( > > Specifically, the "llvm-gcc-i386-darwin9" buildbot here at Apple last > compiled TOT successfully yesterday morning (31aug); that was revision > 80586. By revision 80589, the bootstrap failed due to a miscompare, > and by revision 80610, it's aborting while compiling little pieces of > libgcc. > > 80586 built O.K. (about 8AM, Pacific Standard Time, on Monday 31aug) > ... > 80589 bootstrap miscompare (about one hour after 80586) > ... > 80610 abort()s while compiling libgcc (about two hours after 80589) > ... > 80717 (current as I write this, on Tuesday 01sep) still broken > > I realize that everyone is busy, but I think TOT has been broken long > enough. Would everyone that committed any patches yesterday please > check your work with a clean make of TOT? > > Thank you in advance, > > stuart > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
On Sep 1, 2009, at 2:27 PM, Daniel Dunbar wrote:> Yes, this is pretty unacceptable IMHO. > > I would go revert crazy if I knew what to hit, unfortunately I don't. > > Currently I believe there are two problems, a CallGraphSCC assert > which is firing everywhere (including the clang test suite, *cough*). > This started with 80698. Chris is working on this (if it isn't already > fixed).Fixed in r80724. -Chris
Stuart, On Tue, Sep 1, 2009 at 2:27 PM, Daniel Dunbar<daniel at zuster.org> wrote:> Yes, this is pretty unacceptable IMHO. > > I would go revert crazy if I knew what to hit, unfortunately I don't. > > Currently I believe there are two problems, a CallGraphSCC assert > which is firing everywhere (including the clang test suite, *cough*). > This started with 80698. Chris is working on this (if it isn't already > fixed). > > The bootstrap comparison failures are being looked at by Devang.Yes, I am investigating this. As you say, the buildbots were happy Monday morning, but investigation leads me to combination of patches committed last week and first week of August. The bug was hiding until Monday. So... stay tuned. - Devang