From owner-freebsd-hackers@freebsd.org Sun May 26 12:08:13 2019 Return-Path: Delivered-To: freebsd-hackers@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 530C715A4DA3 for ; Sun, 26 May 2019 12:08:13 +0000 (UTC) (envelope-from db@db.net) Received: from artemis.db.net (artemis.db.net [45.32.229.41]) by mx1.freebsd.org (Postfix) with ESMTP id 7E36E850AF; Sun, 26 May 2019 12:08:12 +0000 (UTC) (envelope-from db@db.net) Received: from night.db.net (artemis.db.net [45.32.229.41]) by artemis.db.net (Postfix) with ESMTP id B3728101B8; Sun, 26 May 2019 12:08:09 +0000 (UTC) Received: by night.db.net (Postfix, from userid 1000) id 5A5B239872; Sun, 26 May 2019 08:08:09 -0400 (EDT) Date: Sun, 26 May 2019 08:08:09 -0400 From: Diane Bruce To: Dimitry Andric Cc: Yuri , Konstantin Belousov , Freebsd hackers list , emaste@freebsd.org, cy@freebsd.org Subject: Re: What is the portable 128-bit floating point type? Message-ID: <20190526120809.GB65430@night.db.net> References: <20190525200437.GV2748@kib.kiev.ua> <20190525210311.GW2748@kib.kiev.ua> <3E0ACABC-D17B-45AD-9810-06ADA52F597A@FreeBSD.org> <6d9857d7-9624-2013-81e0-191c78ed3a4f@rawbw.com> <6183B49B-76F2-4ABF-A6A2-D170C6164553@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6183B49B-76F2-4ABF-A6A2-D170C6164553@FreeBSD.org> User-Agent: Mutt/1.11.4 (2019-03-13) X-Rspamd-Queue-Id: 7E36E850AF X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [3.88 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.66)[0.655,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[db.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.28)[0.282,0]; RCPT_COUNT_FIVE(0.00)[6]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: mx1-us2.ppe-hosted.com]; NEURAL_SPAM_LONG(0.95)[0.954,0]; R_SPF_NA(0.00)[]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:20473, ipnet:45.32.224.0/21, country:US]; MIME_TRACE(0.00)[0:+]; IP_SCORE(0.00)[asn: 20473(0.07), country: US(-0.06)]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 May 2019 12:08:13 -0000 On Sun, May 26, 2019 at 12:02:34PM +0200, Dimitry Andric wrote: > On 26 May 2019, at 02:20, Yuri wrote: > > > > On 2019-05-25 14:30, Dimitry Andric wrote: > >> But from clang's OSTargets.h file, it looks like 128 bit float support > >> is never set to enabled for FreeBSD. > > > > > > If clang supports __float128, and clang is FreeBSD's main compiler, shouldn't it be enabled on FreeBSD then? > > It probably should, but those kinds of things don't just magically appear > out of thin air: Somebody(TM) has to do the actual work to implement the > support, test it, maintain it, and so on. Apparently there has not yet > been any great need for this floating point precision. > > Are you volunteering? :) I've been slowly looking at it already in my copious spare time. It's really something we should be supporting. The libgcc_s wrong version problem is being dealt with by others by linking gfortran with a static version of libgcc_s (!). (As discussed with Cy at BSDCan 2019) See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208120#c24 specifically comment 35 > > -Dimitry > > P.S.: I believe one of the first requirements is a header. > - Diane -- - db@FreeBSD.org db@db.net http://www.db.net/~db