From owner-p4-projects@FreeBSD.ORG Wed Apr 9 13:39:20 2003 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id E09B537B404; Wed, 9 Apr 2003 13:39:19 -0700 (PDT) Delivered-To: perforce@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 894A037B401; Wed, 9 Apr 2003 13:39:19 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id C369443FAF; Wed, 9 Apr 2003 13:39:18 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.9/8.12.7) with ESMTP id h39KcwD0045413; Wed, 9 Apr 2003 13:39:02 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.9/8.12.9/Submit) id h39Kcuhl045412; Wed, 9 Apr 2003 13:38:56 -0700 (PDT) Date: Wed, 9 Apr 2003 13:38:56 -0700 From: "David O'Brien" To: Peter Wemm Message-ID: <20030409203856.GA45368@dragon.nuxi.com> References: <20030409173830.GA549@dhcp01.pn.xcllnt.net> <20030409181005.A975B2A7EA@canning.wemm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030409181005.A975B2A7EA@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 cc: Perforce Change Reviews cc: John Baldwin cc: Marcel Moolenaar Subject: Re: PERFORCE change 28461 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Apr 2003 20:39:21 -0000 On Wed, Apr 09, 2003 at 11:10:05AM -0700, Peter Wemm wrote: > > > This gets hairy... if the toolchain calls it one thing and we call it > > > another. AMD marketing is trying to squash the "x86-64" name in favaor > > > of "AMD64". Note that "AMD64" is what M$ has always called it... so one > > > has to wonder... > > > > I agree with the concerns, but x86-64 is a particularly ugly name > > and uncomfortable to use in general that I'm inclined to prefer a > > name change in spite of the drawbacks. Think about all the scripts > > and makefiles containing x86_64... *shiver* I fail to see what is so ugly about x86-64. I think it is a perfect name that totally indicates what the platform is all about. > Could we live with a slightly modified toolchain that defines both > __x86_64__ and __amd64__ ? I'd be more than happy to rename everything > so that it was #ifdef __amd64__ and have MACHINE_ARCH=amd64 for > $dir/amd64/* etc. But we can't stop defining __x86_64__ since thats what > linux and the FSF camp appear to use. Lots of third party stuff will have > __x86_64__ ifdefs. As many of you know, I'm very close to the name "issue"... perhaps we can just ignore the issue for now, and let me see if I can get our BSD bretheren and toolchain and Linux people to go along with such a name change. I'd really prefer to not be the odd-man out.