Jeffrey A Law wrote:
On Mon, 2005-05-23 at 11:04 -0700, Mark Mitchell wrote:
Jeffrey A Law wrote:
much rather bite the bullet and get them fixed now. The fact that it's
affecting a lot of people keep the coals hot on my feet :-)
Jeff --
I know you're doing everything you can to fix the problems. Do you have
an ETA for a solution? Probably if it's on the order of a day, everyone
can wait; if it's a week, that might be more of a problem.
Depends on how we want to proceed.
Fixing the immediate problem in forwprop.c is trivial as are fixes for
similar problems in other places exposed by Daniel's checking code.
C, C++ and Java look to be in pretty good shape right now.
What's going to be more interesting will be the Fortran failures, which
I expect to start looking at this afternoon. I'd like to hold off
making any kind of estimate or decisions until I've sat down and looked
at the Fortran goop.
Fair enough. Would you mind reporting back later today, then? One
possibility is to do the changes that fix our primary languages (C, C++,
and Java, since it's easy) and deal with Fortran later. If we can get
the mainline bootstrapping and passing regression tests on primary
platforms, but leaving Fortran broken, that might be worthwhile.
--
Mark Mitchell
CodeSourcery, LLC
[EMAIL PROTECTED]
(916) 791-8304
