This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: what should bootstrap *really* do?
- To: kenner at vlsi1 dot ultra dot nyu dot edu
- Subject: Re: what should bootstrap *really* do?
- From: DJ Delorie <dj at redhat dot com>
- Date: Tue, 14 Nov 2000 09:58:59 -0500
- CC: gcc at gcc dot gnu dot org
- References: <10011141106.AA15110@vlsi1.ultra.nyu.edu>
> When would anything of "significance" *not* change?
When the sources don't change. Example: a cron job that updates the
sources from cvs and "make bootstrap"s. If nothing changes, why waste
cycles? The more likely case is a forgetful programmer ("Did I
bootstrap this? Hmmm... make bootstrap... yup, I did.").
> In other words, how would this be different from what we used to
> have to justify the added complexity?
Some developers want it the old way. Some developers want it the new
way. Some developers want something else entirely. Is it so bad to
want to please everyone?
I, personally, want a restartable bootstrap because I, personally,
work on systems that can't reliably complete a full bootstrap. Other
people have other needs. I'm trying to change the system so that more
than one option is available.