This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: GCC bootstrap breakage
- From: "Andrew Pinski" <pinskia at gmail dot com>
- To: "Rafael Espindola" <espindola at google dot com>
- Cc: "Gerald Pfeifer" <gerald at pfeifer dot com>, gcc-patches <gcc-patches at gcc dot gnu dot org>, "Diego Novillo" <dnovillo at google dot com>
- Date: Tue, 4 Mar 2008 23:53:54 -0800
- Subject: Re: GCC bootstrap breakage
- References: <alpine.LSU.1.00.0803050236331.23591@pulcherrima.dbai.tuwien.ac.at> <38a0d8450803042324i66871239qf7ea323f4dfa482a@mail.gmail.com>
On 3/4/08, Rafael Espindola <espindola@google.com> wrote:
> Could be. I am very sorry about that. Working on the tuples branch I
> just got used to using "--disable-bootstrap" :-(
When you get a patch for approval for the trunk that was designed for
a branch, you should reregtest the patch on the trunk to make it does
not break anything else. Also if you use --disable-bootstrap, get
used to using "make bootstrap" (the old style of bootstrapping the
compiler). :) It might be best if you have scripts which do the
building/testing for you and then you just have to compare the
testresults. contrib/gcc_build is already a good script for that
fact. And then you don't have to get used to using
--disable-bootstrap on a specific branch as it is already there.
Anyways Geoff Keating fixed this issue already.
-- Pinski