Re: snapshot still won't bootstrap with BOOT_CFLAGS="-O4 -g"...

[mrs at wrs dot com (Mike Stump)]

> From: N8TM@aol.com
> Date: Mon, 28 Dec 1998 17:37:44 EST

> I have been getting the same failure attempting to bootstrap with
> '-Os -march=pentiumpro' on several platforms for over 2 months now.
> I have debated how loud to complain, don't know to whom to complain

Well, while loudness may work now and then, a high quality complaint
is the best solution.  If you don't know whom to complain to, then
there is more that you can do to help us.  Just check out the
compiler, rebuild and test it from various dates in the past to trace
when it was that it broke.  From there, the changes in the Changelog
will say who broke it (or cvs log, if the didn't leave a changelog
entry).

If you understand what a binary search is, you can use that method
fairly effectively to track down what broke it.

Once you have identified the person, you can then start up a dialog
with them on when they plan to fix it (the person that breaks
something should be willing to fix it).  If they don't have the time,
or are not willing to fix it, then I think asking egcs to remove their
work, on the grounds that it isn't complete yet is best.

cvs update -D '45 days ago' .
make clean; make; test it

is the usual way I do it.  I can sometimes increase search speed by
guessing at Changelog entries that might have broken something, or at
specific files that might have done it.  You can omit clean in come
cases.

Let us know when you have the name of the person that broke stuff (the
changelog entry), and we can go from there.

Without cvs access, you can try snapshot diffs, but sorting stuff out
with them is harder.