From owner-freebsd-amd64@FreeBSD.ORG Wed Jun 22 22:52:02 2005 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 09EB516A41C for ; Wed, 22 Jun 2005 22:52:02 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id DECDC43D53 for ; Wed, 22 Jun 2005 22:52:01 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.13.4/8.13.4) with ESMTP id j5MMq1cn009350; Wed, 22 Jun 2005 15:52:01 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.4/8.13.1/Submit) id j5MMq1rd009349; Wed, 22 Jun 2005 15:52:01 -0700 (PDT) (envelope-from sgk) Date: Wed, 22 Jun 2005 15:52:01 -0700 From: Steve Kargl To: Sean McNeil Message-ID: <20050622225201.GA8836@troutmask.apl.washington.edu> References: <42B409A7.5020909@mail.uni-mainz.de> <42B417C7.80904@samsco.org> <20050619043539.GA46516@dragon.NUXI.org> <20050622221942.GA36733@xor.obsecurity.org> <1119479108.2709.3.camel@server.mcneil.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1119479108.2709.3.camel@server.mcneil.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org, Kris Kennaway Subject: Re: 6.0-Current and gcc 4.x X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jun 2005 22:52:02 -0000 On Wed, Jun 22, 2005 at 03:25:08PM -0700, Sean McNeil wrote: > On Wed, 2005-06-22 at 18:19 -0400, Kris Kennaway wrote: > > > > The ABI breakage at numerous points early in the GCC 3.x branch was > > extremely disruptive. > > This is the amd64 mailing list, so I assume you are talking about amd64 > machines and I thought the architecture wasn't really supported before > GCC 3.x. In any event, I doubt there would be any such disruption > between 3.x and 4.x. The amd64 ABI is pretty solid now, correct? > The machine description for amd64 may not have changed. The ABI breakage may have occurred at the shared library level. GCC is preparing an early release of 4.0.1 in part to address breakage where KDE does not work correctly and/or can't even be compiled with 4.0.0. -- Steve