From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/9612 Path: news.gmane.org!not-for-mail From: Bobby Bingham Newsgroups: gmane.linux.lib.musl.general Subject: Re: long double on powerpc64 Date: Mon, 14 Mar 2016 15:13:12 -0500 Message-ID: <20160314201311.GB1116@dora.lan> References: <20160311031636.GA3851@gordon.members.linode.com> <20160311041759.GU9349@brightrain.aerifal.cx> <20160311130434.GE29662@port70.net> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1457986419 31637 80.91.229.3 (14 Mar 2016 20:13:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 14 Mar 2016 20:13:39 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-9625-gllmg-musl=m.gmane.org@lists.openwall.com Mon Mar 14 21:13:35 2016 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1afYrr-0005CM-R7 for gllmg-musl@m.gmane.org; Mon, 14 Mar 2016 21:13:31 +0100 Original-Received: (qmail 14177 invoked by uid 550); 14 Mar 2016 20:13:26 -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 14158 invoked from network); 14 Mar 2016 20:13:25 -0000 Content-Disposition: inline In-Reply-To: <20160311130434.GE29662@port70.net> X-Operating-System: Linux dora 4.3.3 User-Agent: Mutt/1.5.24 (2015-08-30) Xref: news.gmane.org gmane.linux.lib.musl.general:9612 Archived-At: On Fri, Mar 11, 2016 at 02:04:35PM +0100, Szabolcs Nagy wrote: > if long double is 64bit then the 128bit hw floats cannot be used > with musl, because we don't want library support for __float128. >=20 > note that the glibc position is that for __float128 support the > minimum required gcc version has to change to gcc-7 because it is > abi and libc needs complex support (which will not be in gcc-6 yet). > https://gcc.gnu.org/ml/gcc-patches/2015-12/msg02222.html > https://sourceware.org/ml/libc-alpha/2016-03/msg00193.html >=20 > the problem with -ld64 suffix is that gcc-6 already has hardcoded > dynamic linker names (i don't think we can change that now, before > the gcc-6 release). >=20 > so i'd leave the dynlinker name as is, use 64bit ld for now and > rediscuss the issue when ieee128 long double works in gcc-7 I'd forgotten about GCC needing to know the dynlinker name. I agree with your suggestions here.