This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: what should bootstrap *really* do?
- To: Hans-Peter Nilsson <hans-peter dot nilsson at axis dot com>
- Subject: Re: what should bootstrap *really* do?
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 14 Nov 2000 16:16:17 -0200
- Cc: kenner at vlsi1 dot ultra dot nyu dot edu, gcc at gcc dot gnu dot org
- Organization: GCC Team, Red Hat
- References: <200011141800.TAA32584@ignucius.axis.se>
On Nov 14, 2000, Hans-Peter Nilsson <hans-peter.nilsson@axis.com> wrote:
>> From: Alexandre Oliva <aoliva@redhat.com>
>> Date: 14 Nov 2000 15:54:01 -0200
>> On Nov 14, 2000, kenner@vlsi1.ultra.nyu.edu (Richard Kenner) wrote:
>>
>> > [No, I (H-P) wrote this, don't blame Kenner for it:]
>> > Then why not have a *new* target with the *new* (restart-in-middle)
>> > functionality instead of changing the "bootstrap" target? The name
>> > "bootstrap-restart" comes to mind. :-)
>>
>> > That's my current thinking as well.
>>
>> My expectation from `bootstrap-restart' is that it would start
>> bootstrap from stratch, not proceed from where it stopped last time.
> Ok, bad name. Not a native speaker and so on.
> Perhaps bootstrap-continue?
I already find it bad enough that the default rule is not the one we
recommend for users. IMHO, adding more complexity to that is a bad
idea. I'd rather keep `bootstrap' simple for end users (i.e., have it
proceed from the point in which it stopped, for whatever reason) and
create alternate rules for developers.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me