This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: m68k-*-*bsd `Internal compiler error' mostly tracked down
- To: Marc dot Espie at liafa1 dot liafa dot jussieu dot fr, egcs-bugs at cygnus dot com
- Subject: Re: m68k-*-*bsd `Internal compiler error' mostly tracked down
- From: mrs at wrs dot com (Mike Stump)
- Date: Tue, 24 Feb 1998 12:44:09 -0800
> From: espie@quatramaran.ens.fr (Marc Espie)
> Date: Tue, 24 Feb 1998 17:43:24 +0100
> - is there any simple way I could get a detailed history of what was
> changed between 971215 and 971225? Especially coherent changes to
> the g++ code. - what should I look for?
Yes, take a look at the ChangeLog files (gcc/ChangeLog and
gcc/cp/ChangeLog). Then, you can take a look at cvs diff -D 'before'
-D 'after', or even cvs update -D 'whenever', and try compilers
inbetween. If you know how to binary search, you can shorten the time
required to find it. Once you narrow it does to one change in the
ChangeLog, you pretty much have the culprit caught.
If someone would build a compiler each day and archive it, when
someone else reports a new problem you can then binary search on
prebuilt compilers and find when the problems went in fairly quickly.
$150 for 4 GB is a lot of compilers for not much money.