From owner-freebsd-current Tue Oct 8 17:46:11 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 580BF37B401; Tue, 8 Oct 2002 17:46:10 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id C78A543E42; Tue, 8 Oct 2002 17:46:09 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.6/8.12.2) with ESMTP id g990k65b015113; Tue, 8 Oct 2002 17:46:06 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.6/8.12.5/Submit) id g990jw4o015105; Tue, 8 Oct 2002 17:45:58 -0700 (PDT) Date: Tue, 8 Oct 2002 17:45:58 -0700 From: "David O'Brien" To: Peter Wemm Cc: John Baldwin , Alexander Kabaev , current@FreeBSD.org, Dag-Erling Smorgrav Subject: Re: i386 tinderbox failure Message-ID: <20021009004558.GA15075@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org Mail-Followup-To: David O'Brien , Peter Wemm , John Baldwin , Alexander Kabaev , current@FreeBSD.org, Dag-Erling Smorgrav References: <20021008224042.GA13880@dragon.nuxi.com> <20021008231042.247562A88D@canning.wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021008231042.247562A88D@canning.wemm.org> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 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 Tue, Oct 08, 2002 at 04:10:42PM -0700, Peter Wemm wrote: > "David O'Brien" wrote: > > On Tue, Oct 08, 2002 at 03:55:36PM -0400, John Baldwin wrote: > > > Could you please just commit this on the vendor branch if it is the > > > vendor fix for now. Since the next vendor import will contain the > > > fix you don't need to worry about maintaining the local patch so > > > committing it onto the vendor branch is ok. > > > > Doing this screws up diffs to vendor source as there won't be a tag that > > corisponds with this across all files. For small contribed things that > > is OK. But when doing large ones it the following import+merge becomes > > harder. > > While that is true, it usually isn't all that big a deal if you are careful > and keep track of what you've done. It is certainly better than causing > the file to leave the vendor branch for something you *know* is now in the > vendor tree. And I think its better than leaving a known 'compiler crash' > case there to bite developers. I'm hoping for another 3.2.1 import soon. I raised some hell on the GCC lists last week about the quality of 3.2.1; and actually got some Athlon and p4 optimization PR's taken care of. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message