From owner-freebsd-arm@FreeBSD.ORG Wed Feb 11 19:56:05 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E74679BF for ; Wed, 11 Feb 2015 19:56:04 +0000 (UTC) Received: from anacreon.physics.berkeley.edu (anacreon.Physics.Berkeley.EDU [128.32.117.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "anacreon.physics.wisc.edu", Issuer "anacreon.physics.wisc.edu" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C9C6D17D for ; Wed, 11 Feb 2015 19:56:04 +0000 (UTC) Received: from anacreon.physics.berkeley.edu (localhost [127.0.0.1]) by anacreon.physics.berkeley.edu (8.14.9/8.14.9) with ESMTP id t1BJYDBF062470; Wed, 11 Feb 2015 11:34:13 -0800 (PST) (envelope-from nwhitehorn@freebsd.org) Message-ID: <54DBAEB5.6030007@freebsd.org> Date: Wed, 11 Feb 2015 11:34:13 -0800 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD powerpc; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Michael Mitchell Subject: Re: FreeBSD/arm64 MACHINE/MACHINE_ARCH identification References: <54DB9D93.6070702@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Feb 2015 19:56:05 -0000 I think you have misunderstood my point. Where there is substantial overlap between architectures (e.g. 32-bit and 64-bit PowerPC, 32-bit and 64-bit MIPS, big- and little-endian versions of architectures), we usually set MACHINE and MACHINE_CPUARCH to something common (e.g. "arm", "powerpc", "mips") and MACHINE_ARCH to the 32-/64-/big-endian/little-endian variant name. So in this case, MACHINE would be "arm" and MACHINE_ARCH "aarch64", just as we now have arm/armv6, arm/armeb, etc. -Nathan On 02/11/15 11:27, Michael Mitchell wrote: > why swim upstream on a naming convention that is established? > > when you say arm64 how many people are going to read that as amd64? > > other than cosmetic, is there a technical rationale for picking a > different naming convention other than what the industry uses? > > On Wed, Feb 11, 2015 at 10:21 AM, Nathan Whitehorn > > wrote: > > > On 02/11/15 09:41, Ed Maste wrote: > > The FreeBSD/arm64 work in progress currently reports "arm64" for the > machine and processor type - i.e., uname -m and uname -p. > > > It would probably also be good if we had MACHINE = arm here. > -Nathan > > > It seems that the official, awkward name aarch64 is broadly used > elsewhere - for example, in toolchain triples and autoconf > tests. To > save us grief in the future I think it is worth following suit: > > diff --git a/sys/arm64/include/param.h b/sys/arm64/include/param.h > index 5cd0445..525a0e7 100644 > --- a/sys/arm64/include/param.h > +++ b/sys/arm64/include/param.h > @@ -43,10 +43,10 @@ > #define STACKALIGN(p) ((uint64_t)(p) & ~STACKALIGNBYTES) > > #ifndef MACHINE > -#define MACHINE "arm64" > +#define MACHINE "aarch64" > #endif > #ifndef MACHINE_ARCH > -#define MACHINE_ARCH "arm64" > +#define MACHINE_ARCH "aarch64" > #endif > > I'm not proposing that we rename any of the source files. I believe > this approach is consistent with the Debian project - they call > it the > "arm64" port, but report aarch64 from uname. > > I believe it will be much easier for us to carry around any > special-case s/aarch64/arm64/ in the base system (if necessary) than > trying to teach third-party software that the FreeBSD 64-bit ARM > architecture is called arm64 instead of aarch64. > > Any objections or concerns? > _________________________________________________ > freebsd-arm@freebsd.org mailing > list > http://lists.freebsd.org/__mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to > "freebsd-arm-unsubscribe@__freebsd.org > " > > > _________________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/__mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to > "freebsd-arm-unsubscribe@__freebsd.org > " > >