From owner-freebsd-current Sun Sep 1 15: 2:32 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B83F337B43D; Sun, 1 Sep 2002 15:02:13 -0700 (PDT) Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09AFC43E4A; Sun, 1 Sep 2002 15:02:13 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id g81M2Bv10811; Sun, 1 Sep 2002 15:02:11 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Sun, 1 Sep 2002 15:00:36 -0700 (PDT) From: Matthew Jacob Reply-To: To: Alexander Kabaev Cc: , Subject: Re: HEADS UP: GCC 3.2 in progress In-Reply-To: <20020901175759.24d5b9a2.ak03@gte.com> Message-ID: <20020901145843.B16984-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 1 Sep 2002, Alexander Kabaev wrote: > On Sun, 1 Sep 2002 14:50:50 -0700 (PDT) > Matthew Jacob wrote: > > > From recent experience it is my estimation that a gcc upgrade sets 5.0 > > development back a month (that is, the last GCC upgrade kept *me* from > > working productively for around a month due to various this thats and > > the others). If that's what people want, that's fine. I could also be > > totally wrong, and this won't break things. I'm just a bit startled > > that this appears out of nowhere (I sure don't recall it being > > discussed) and just happens, with 10 minutes warning. > > Matt, the change was discussed several times on developers@, so this > import is hardly 'out of nowhere'. I sure didn't see anything on the recent 5.0 schedule about this. Like I said- this is not meant to be hypercritical. Let's assume that I'm not paying that close attention, like a *lot* of developers to the flood of mail. There might have been a note about "new compiler import" on the recent 5.X schedule changes that surely would catch the eye. > > > This is, IMO, why FreeBSD is not going to be very successful. You > > cannot just make major toolchain changes w/o at least *some* belief > > that this is going to be done well. Did you do a dryrun with the > > import before checking things in? > > About five buildworlds on i386 and two on Alpha. Does that count as dry > runs? Surely they do. Did somebody in ia64 && sparc && ppc get a headsup? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message