breakage on the 3.0 branch.

Carlo Wood carlo@alinoe.com
Sun Feb 25 08:09:00 GMT 2001


On Sun, Feb 25, 2001 at 09:45:20AM -0600, Robert Lipe wrote:
> Someone killed the bootstrap yesterday.   The smoking gun looks like
> either loop or i386 changes.
> 
> ----- Forwarded message from Robert Lipe <robertl@sco.com> -----
> 
> To: robertl@rjlhome.sco.com
> 
> Updating CVS tree
> P gcc/ChangeLog
> P gcc/errors.c
> P gcc/errors.h
> P gcc/loop.c
> P gcc/version.c
> P gcc/config/i386/i386-protos.h
> P gcc/config/i386/i386.c
> P gcc/config/i386/i386.md
> P gcc/f/version.c
> M gcc/java/parse.c
> P gcc/testsuite/ChangeLog
> U gcc/testsuite/gcc.c-torture/execute/20010224-1.c
> P libf2c/libF77/Version.c
> P libf2c/libI77/Version.c
> P libf2c/libU77/Version.c
> Adjusting file timestamps

This is what did break it for me:

/usr/src/gcc>gcc_build-3.0 update
Updating CVS tree
P gcc/ChangeLog
P gcc/loop.c
P gcc/config/i386/i386-protos.h
P gcc/config/i386/i386.c
P gcc/config/i386/i386.md
P gcc/testsuite/ChangeLog
U gcc/testsuite/gcc.c-torture/execute/20010224-1.c
Adjusting file timestamps

Although a little closer to the errornous commit,
not really giving new information I guess ;)
-- 
Carlo Wood <carlo@alinoe.com>



More information about the Gcc mailing list