This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: gcc development schedule [Re: sharing libcpp between GDB and GCC]
- From: "David O'Brien" <obrien at FreeBSD dot org>
- To: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Cc: overseers at gcc dot gnu dot org, Zack Weinberg <zack at codesourcery dot com>, gcc at gcc dot gnu dot org, gdb at sources dot redhat dot com, jimb at redhat dot com
- Date: Thu, 28 Mar 2002 08:58:14 -0800
- Subject: Re: gcc development schedule [Re: sharing libcpp between GDB and GCC]
- Organization: The NUXI BSD group
- References: <20020328034552.GB23767@codesourcery.com> <Pine.BSF.4.44.0203281016560.83412-100000@pulcherrima.dbai.tuwien.ac.at>
- Reply-to: obrien at FreeBSD dot org
On Thu, Mar 28, 2002 at 10:22:49AM +0100, Gerald Pfeifer wrote:
> On Wed, 27 Mar 2002, Zack Weinberg wrote:
> >>> (E.g. it takes about 10x longer to do "cvs update" on the 3.0
> >>> branch than the trunk.)
> >> Yeah, what's up with that? (I thought it was just me.)
>
> Same here.
>
> On the gcc-3.1 branch, I'm approaching the situation where cvs update
> takes longer than bootstrapping the compiler (with C and C++ frontends).
That is only because one must go across the network to do 'cvs up'.
When are public CVSup servers going to be made available? A bootstrap on
a fast machine takes 30 minutes. It does not take anywhere near that
long to 'cvs up' GCC from a local repository.
For those not wanting a local copy of the repository, CVSup in "check out
mode" (gives same results as 'cvs co' or 'cvs up' is 4x faster than
using CVS directly).
--
-- David (obrien@FreeBSD.org)