From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 22 19:02:22 2004 Return-Path: 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 BA2DE16A4CE; Sun, 22 Feb 2004 19:02:22 -0800 (PST) Received: from bigtex.jrv.org (rrcs-sw-24-73-246-106.biz.rr.com [24.73.246.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5809C43D2D; Sun, 22 Feb 2004 19:02:22 -0800 (PST) (envelope-from james@bigtex.jrv.org) Received: from bigtex.jrv.org (localhost [127.0.0.1]) by bigtex.jrv.org (8.12.1/8.12.1) with ESMTP id i1N32Jo8045700 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 22 Feb 2004 21:02:19 -0600 (CST) Received: (from james@localhost) by bigtex.jrv.org (8.12.1/8.12.1/Submit) id i1N32IgU045697; Sun, 22 Feb 2004 21:02:18 -0600 (CST) Date: Sun, 22 Feb 2004 21:02:18 -0600 (CST) Message-Id: <200402230302.i1N32IgU045697@bigtex.jrv.org> From: James Van Artsdalen To: peter@wemm.org In-reply-to: <200402220057.36903.peter@wemm.org> (message from Peter Wemm on Sun, 22 Feb 2004 00:57:36 -0800) References: <200402220057.36903.peter@wemm.org> cc: amd64@freebsd.org cc: adridg@cs.kun.nl cc: gerald@pfeifer.com cc: freebsd-amd64@freebsd.org Subject: Re: AMD64 and lang/gcc3x on -CURRENT X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2004 03:02:22 -0000 > From: Peter Wemm > Date: Sun, 22 Feb 2004 00:57:36 -0800 > > On Wednesday 18 February 2004 12:37 am, Gerald Pfeifer wrote: > > > 1) AMD didn't give the platform an official name till fairly late > > > 2) Some folks chose amd64 > > > 3) Later the muttonheads at the FSF chose x86_64 > > > > And right they were. See yesterdays press announcement by Intel. > > That sequence of events isn't quite right. AMD originally came up with > x86-64. When Microsoft got going on the port, they said "that name > sucks to type, how about amd64? We're NOT using x86=64". And so it > became "amd64" or AMD64. And FWIW, I agree. x86_64 is the worst > possible name to type. My understanding is that the linux crowd picked x86_64 and Microsoft and FreeBSD picked amd64. At this point everyone, except Microsoft, has done releases and systems are deployed and in the field. It's too late to go back and make changes without good reason: configure scripts need to accept both. Why not something like to solve the heartburn? There's still a collision of some sort between freebsd.h and x86_64.h that needs to be solved, but that's a different issue. *** config.guess.~1~ Thu Jan 30 17:25:36 2003 --- config.guess Sun Feb 22 20:41:42 2004 *************** *** 759,764 **** --- 759,767 ---- #endif EOF eval `$CC_FOR_BUILD -E $dummy.c 2>/dev/null | grep ^LIBC=` + if [ ".$UNAME_MACHINE" = ".amd64" ] ; then + UNAME_MACHINE=x86_64 + fi echo ${UNAME_MACHINE}-unknown-freebsd`echo ${UNAME_RELEASE}|sed -e 's/[-(].*//'`${LIBC:+-$LIBC} exit 0 ;; i*:CYGWIN*:*)