From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/11061 Path: news.gmane.org!.POSTED!not-for-mail From: Szabolcs Nagy Newsgroups: gmane.linux.lib.musl.general Subject: Re: musl-cross-make build script. Date: Sat, 18 Feb 2017 14:39:22 +0100 Message-ID: <20170218133921.GL12395@port70.net> References: <20170217115321.GH12395@port70.net> <3fa40871-36f0-9d82-6602-f929ece76de6@se-instruments.com> <20170218125301.GK12395@port70.net> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1487425183 7958 195.159.176.226 (18 Feb 2017 13:39:43 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 18 Feb 2017 13:39:43 +0000 (UTC) User-Agent: Mutt/1.6.0 (2016-04-01) To: Rob Landley , musl Original-X-From: musl-return-11076-gllmg-musl=m.gmane.org@lists.openwall.com Sat Feb 18 14:39:31 2017 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1cf5EX-0000yi-Qk for gllmg-musl@m.gmane.org; Sat, 18 Feb 2017 14:39:29 +0100 Original-Received: (qmail 9924 invoked by uid 550); 18 Feb 2017 13:39:34 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 9903 invoked from network); 18 Feb 2017 13:39:33 -0000 Mail-Followup-To: Rob Landley , musl Content-Disposition: inline In-Reply-To: <20170218125301.GK12395@port70.net> Xref: news.gmane.org gmane.linux.lib.musl.general:11061 Archived-At: * Szabolcs Nagy [2017-02-18 13:53:01 +0100]: > in a triplet "armv8" means the armv8 architecture in > 32bit execution state (which arm calls aarch32) and > that is backward compatible (and almost identical to) > armv7 (at least the -a profile, armv8-m and armv7-m > have more differences afaik) > > in a triplet "aarch64" means the armv8 architecture in > 64bit execution state. > > so if you configure for armv8l-linux-musleabihf you > get a toolchain that follows a 32bit arm abi and uses > a 32bit arm isa (thumb or arm like with armv7). > > the 64bit triplet is aarch64-linux-musl (there is no > soft float abi nor eabi suffix), there is an ilp32 > abi for aarch64 which uses 64bit isa (like x32) which > is not supported by musl, and a bigendian variant > which can be configured with "aarch64_be" (but not > used in practice i think). one more note: there are various isa levels and extensions, e.g. --with-arch=armv8.2-a+crypto+fp16 will configure for armv8.2-a isa level with the optional crypto and 16bit float instructions enabled. (this affects both 32bit and 64bit arm isas) there is no softfloat abi, but you can still compile something without float instructions using cflag like -march=armv8-a+nofp (the -mgeneral-regs-only flag works too, but +noXXX is a generic way to turn extensions off.. so there is a zoo of variants, but binary distros will care about the baseline armv8-a only i guess)