From owner-freebsd-current@freebsd.org Wed Mar 28 20:24:17 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 07729F722B8 for ; Wed, 28 Mar 2018 20:24:17 +0000 (UTC) (envelope-from AWilcox@Wilcox-Tech.com) Received: from mail.wilcox-tech.com (mail.wilcox-tech.com [45.32.83.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.wilcox-tech.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6C353812BE for ; Wed, 28 Mar 2018 20:24:16 +0000 (UTC) (envelope-from AWilcox@Wilcox-Tech.com) Received: (qmail 15553 invoked from network); 28 Mar 2018 20:17:31 -0000 Received: from 107-131-85-28.lightspeed.tulsok.sbcglobal.net (HELO ?192.168.1.237?) (awilcox@wilcox-tech.com@107.131.85.28) by mail.wilcox-tech.com with ESMTPA; 28 Mar 2018 20:17:31 -0000 Subject: Re: From LLVM: I got a note that LLVM plans to remove PPC64's V1 abi support; I'm asked about what support there is for the PPC64 little-endian/V2 abi (see forwarded message) To: Nathan Whitehorn , Sean Fertile , marklmi26-fbsd@yahoo.com Cc: chmeeedalf@gmail.com, emaste@freebsd.org, freebsd-current@freebsd.org, freebsd-ppc@freebsd.org References: From: "A. Wilcox" Message-ID: <7e000df1-6f91-b255-3548-3faa2968d17e@Wilcox-Tech.com> Date: Wed, 28 Mar 2018 15:17:54 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="JPTEQkTl4zjt8z543zTbGgrOHbVwPzMRE" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Mar 2018 20:24:17 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --JPTEQkTl4zjt8z543zTbGgrOHbVwPzMRE Content-Type: multipart/mixed; boundary="RW28kyw8aStgcFj2C1YJKzrQfODWanLqh"; protected-headers="v1" From: "A. Wilcox" To: Nathan Whitehorn , Sean Fertile , marklmi26-fbsd@yahoo.com Cc: chmeeedalf@gmail.com, emaste@freebsd.org, freebsd-current@freebsd.org, freebsd-ppc@freebsd.org Message-ID: <7e000df1-6f91-b255-3548-3faa2968d17e@Wilcox-Tech.com> Subject: Re: From LLVM: I got a note that LLVM plans to remove PPC64's V1 abi support; I'm asked about what support there is for the PPC64 little-endian/V2 abi (see forwarded message) References: In-Reply-To: --RW28kyw8aStgcFj2C1YJKzrQfODWanLqh Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 03/28/18 13:38, Nathan Whitehorn wrote: > Is this big-endian support or V1 support being removed? We support=20 > the V2 ABI fully on FreeBSD, but not (yet) little-endian. Like on=20 > Linux, the default ABI on big-endian will likely remain V1 for the=20 > indefinite future, This is an important distinction to make (big-endian !=3D ELFv1, and ELFv= 1 !=3D big-endian). But do note that on Linux, the musl libc (in use by distros like Alpine, Ad=C3=A9lie, postmarketOS) only supports ELFv2, even in big-endian mode. = And as the maintainer of Ad=C3=A9lie using it as a daily-driver on an iMac G5= , it's definitely something you can use (the only breakage I've seen so far on Linux is the PCRE JIT ignoring __CALL_ELF and inserting function descriptors anyway). So I wouldn't discount moving to ELFv2 ABI on BE if that is necessary to keep LLVM happy. It'd be some effort but it should work. If this is really something FreeBSD is interested in, you might even manage to convince me to put on my ports hat again, to help get the JIT patches in that are needed for upstreams that went comatose. Best, --arw > however, and it would be good if it were at least simple to re-add=20 > support at some later date. -Nathan >=20 --=20 A. Wilcox (awilfox) Open-source programmer (C, C++, Python) https://code.foxkit.us/u/awilfox/ --RW28kyw8aStgcFj2C1YJKzrQfODWanLqh-- --JPTEQkTl4zjt8z543zTbGgrOHbVwPzMRE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjNyWOYPU1SaTSMHHyynLUZIrnRQFAlq7+HIACgkQyynLUZIr nRTVaw//Q2LNcz77vojZsBmTEtDO6Va+6rudqKz4S8+xxZtdS/uPCRCq1VlyzQqh pTie8lRxHxy7VhbAhtdBE/p1bJrbQRd28/BSFcSgA+8fXpV09EYi4DHuF6rpPKZr NSJeYfLJSCX4RmI3vsV66oO9qOKklBuOFPEhlJGxKK2VE51XfefAlQAEWcL0nCmK svluVNH8EZQHm5SLEX0Takm9K98WA+8nskYw2wC2kfko9tZfoBQFSgCzBMBdRlBQ /oRzuYAkp4VciucjiYQvdSqQki+hSz+7Ms5reZ8IhteFxn+AvrwmuVhUCkC7sXDh Dbb0FcHS6oSVjsqH9eMdgR4YWVvVzajXnfVFLS1mhfs9RQwZEfKAbhIvJY+Yti8y yPWcGvxGYRZtSJ3atsLZGdybq8r93eyJYsn2hSsTE/UjZKcpUr3VWswZc4XiWoJ+ vngrl6wWK2Sq1JMIJtUyUyY3FxhsflAvn8Pt8o2a9ROz5bH9WwPq/1SCvCNVif7/ tUhetraLRrhvuNFoQOXo4XYFrDMhkUWyICL0yWsxLhW6OXQVZ6scp4jHHb3PfMhT j/dBH+kWaVc5TMsEcW8YHqN2mgpbeD4lHUsGPuR/Lg7zedt6sQNMXZ6PJSaSxDED k7p47/fzuEPHXeYNlKHoOQUT+rWghJ55110O1M4sh7Jgc7pnUKA= =57Z8 -----END PGP SIGNATURE----- --JPTEQkTl4zjt8z543zTbGgrOHbVwPzMRE--