This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [patch] Split config.build out from config.gcc

From: Nathanael Nerode <neroden at twcny dot rr dot com>
To: Alexandre Oliva <aoliva at redhat dot com>
Cc: gcc-patches at gcc dot gnu dot org
Date: Fri, 29 Aug 2003 23:54:12 -0400
Subject: Re: [patch] Split config.build out from config.gcc
References: <20030829220750.GA14426@twcny.rr.com> <200308292235.h7TMZi306340@greed.delorie.com> <or1xv483cx.fsf@livre.redhat.lsd.ic.unicamp.br>

Alexandre Oliva wrote:

On Aug 29, 2003, DJ Delorie <dj@redhat.com> wrote:

Alex, DJ, opinions? Is this OK?

I like the idea of breaking config.gcc up, but I really think we
should have one big case with each platform's code grouped by
platform, not multiple cases grouped by feature.  The platform
maintainers will want it that way.  Comments on that?

I agree with DJ.

Will send updated patch. :-)

Maybe we should somehow enable config.gcc to tell whether it's being
run for build, host or target, such that certain pieces of code can be
run conditionally?

I think it's better to break it into three separate files. :-( It can currently tell which it's being run for, and it has only made it uglier.

Follow-Ups:
- Re: [patch] Split config.build out from config.gcc
  - From: DJ Delorie

References:
- [patch] Split config.build out from config.gcc
  - From: Nathanael Nerode
- Re: [patch] Split config.build out from config.gcc
  - From: DJ Delorie
- Re: [patch] Split config.build out from config.gcc
  - From: Alexandre Oliva

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]