From owner-freebsd-arm@FreeBSD.ORG Wed Feb 11 17:56:09 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 CEBF3372; Wed, 11 Feb 2015 17:56:09 +0000 (UTC) Received: from pmta1.delivery3.ore.mailhop.org (pmta1.delivery3.ore.mailhop.org [54.191.214.36]) by mx1.freebsd.org (Postfix) with ESMTP id AD904217; Wed, 11 Feb 2015 17:56:09 +0000 (UTC) Received: from smtp2.ore.mailhop.org (172.31.18.134) by pmta1.delivery1.ore.mailhop.org id hrebra20r84b; Wed, 11 Feb 2015 17:45:57 +0000 (envelope-from ) Received: from [73.34.117.227] (helo=ilsoft.org) by smtp2.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YLbMP-0001EF-2N; Wed, 11 Feb 2015 17:46:01 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t1BHjsMW090712; Wed, 11 Feb 2015 10:45:54 -0700 (MST) (envelope-from ian@freebsd.org) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX180eQK1hY/k4hZpJ3dJAYKc Message-ID: <1423676754.80968.39.camel@freebsd.org> Subject: Re: FreeBSD/arm64 MACHINE/MACHINE_ARCH identification From: Ian Lepore To: Ed Maste Date: Wed, 11 Feb 2015 10:45:54 -0700 In-Reply-To: References: Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.12.8 FreeBSD GNOME Team Port Mime-Version: 1.0 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 17:56:09 -0000 On Wed, 2015-02-11 at 12:41 -0500, 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 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? That sounds good to me, but we're going to use it consistantly everywhere an arch name is needed, right? Like "make TARGET_ARCH=aarch64 ..." and so on? -- Ian