Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 Feb 2019 07:56:54 -0800
From:      Steve Kargl <sgk@troutmask.apl.washington.edu>
To:        Ed Maste <emaste@freebsd.org>
Cc:        Diane Bruce <db@db.net>, =?utf-8?Q?T=C4=B3l?= Coosemans <tijl@freebsd.org>, FreeBSD Ports ML <freebsd-ports@freebsd.org>, Eugene Grosbein <eugen@grosbein.net>
Subject:   Re: FreeCAD 0.17 && /lib//libgcc_s.so.1
Message-ID:  <20190222155654.GA32886@troutmask.apl.washington.edu>
In-Reply-To: <CAPyFy2AexZF8XoP2X3JC76SmVDooPZZDF_WC%2BvhV0gVhxGuiqw@mail.gmail.com>
References:  <a2102b4e-7d7a-7d5b-2ba1-b9a14f8574f6@pinyon.org> <f6a45ec9-7ae4-d9ba-f71c-f2ef8c235039@grosbein.net> <416689e6-37f9-17ec-54d8-0d224c26f30f@pinyon.org> <20190217151604.GB68620@night.db.net> <20190221180515.39c79ce6@kalimero.tijl.coosemans.org> <20190221183040.GA42303@night.db.net> <20190221214646.GA86448@troutmask.apl.washington.edu> <CAPyFy2AexZF8XoP2X3JC76SmVDooPZZDF_WC%2BvhV0gVhxGuiqw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 22, 2019 at 09:32:03AM -0500, Ed Maste wrote:
> On Thu, 21 Feb 2019 at 16:47, Steve Kargl
> <sgk@troutmask.apl.washington.edu> wrote:
> >
> > The missing symbols are
> >
> > % objdump -x lib/libgfortran.so | grep GCC_4.6.0 | awk '{print $5}' | sort
> 
> Thank you for collecting these.
> 
> > It looks like we may be able to grab some of these from libc/softfloat:
> > getf2.c, gttf2.c, letf2.c, lttf2.c, netf2.c.
> >
> > It looks like we might be able to grab a few more from NetBSD:
> > eqtf2.c and unordtf2.c
> 
> All seven of these are available in compiler-rt, I believe they just
> need to be built and added to the version map.
> 
> That leaves: __addtf3 __divtf3 __floatditf __floatsitf __floatunditf
> __multf3 __subtf3
> 
> compiler-rt also has these, but provided only in this case:
> #if defined(CRT_HAS_128BIT) && defined(CRT_LDBL_128BIT)

gfortran provides a REAL(16) type, which is an implementation
of IEEE 754 binary128.  If the architecture has a 128-bit float
type such as sparc64, there isn't a problem.  If the 128-bit
is available from the architecture such as i386, then it uses
GCC __float128 software implementation.  If compiler-rt has
these functions, are they compatiable with GCC's __float128.

-- 
Steve



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190222155654.GA32886>