From: "A. Wilcox" <AWilcox@Wilcox-Tech.com>
To: musl@lists.openwall.com
Subject: Re: musl + PowerPC + GCC 5
Date: Wed, 14 Dec 2016 22:11:49 -0600 [thread overview]
Message-ID: <58521805.5000308@Wilcox-Tech.com> (raw)
In-Reply-To: <20161214105306.GG16379@port70.net>
[-- Attachment #1: Type: text/plain, Size: 2276 bytes --]
On 14/12/16 04:53, Szabolcs Nagy wrote:
> * A. Wilcox <awilfox@adelielinux.org> [2016-12-14 04:02:39 -0600]:
> i think the simplest fix is to config with --disable-decimal-float
/usr/src/sys-devel/gcc-5.4.0-r2/work/gcc-5.4.0/configure
--host=powerpc-foxkit-linux-musl --target=powerpc-foxkit-linux-musl
--prefix=/usr --bindir=/usr/powerpc-foxkit-linux-musl/gcc-bin/5.4.0
--includedir=/usr/lib/gcc/powerpc-foxkit-linux-musl/5.4.0/include
--datadir=/usr/share/gcc-data/powerpc-foxkit-linux-musl/5.4.0
--mandir=/usr/share/gcc-data/powerpc-foxkit-linux-musl/5.4.0/man
--infodir=/usr/share/gcc-data/powerpc-foxkit-linux-musl/5.4.0/info
--with-gxx-include-dir=/usr/lib/gcc/powerpc-foxkit-linux-musl/5.4.0/include/g++-v5
--enable-languages=c,c++,fortran --enable-obsolete --enable-secureplt
--disable-werror --with-system-zlib --enable-nls
--without-included-gettext --enable-checking=release
--enable-libstdcxx-time --enable-shared --enable-threads=posix
--disable-multilib --disable-altivec --disable-fixed-point
--disable-decimal-float --disable-libgcj --enable-libgomp
--disable-libmudflap --enable-libssp --disable-libcilkrts
--disable-libmpx --disable-vtable-verify --disable-libvtv --enable-lto
--without-isl --disable-libsanitizer
Note "--disable-decimal-float". I receive the same error.
> the second simplest fix is to patch the ifdef logic (e.g. define
> BFP_FMT "%Le") but then the conversion code would be broken at
> runtime: the code is compiled with -mlong-double-128 and musl
> expects 64 bit long double. (most likely the bootstrap process
> does not depend on this to work so this is a workaround hack
> that only breaks 128bit float to decimal conversion.)
That sounds unacceptable for production code. I do not understand the
inner workings of floating point though.
> the correct way on musl is to build libgcc without -mlong-double-128
> and without all the 128bit (TF mode) float stuff, but this may need
> some configure and build system changes as i don't immediately see
> an option to turn tf mode things off.
I cannot seem to disable -mlong-double-128 no matter what I patch. :(
Regards,
--arw
--
A. Wilcox (awilfox)
Open-source programmer (C, C++, Python)
https://code.foxkit.us/u/awilfox/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-12-15 4:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 10:02 A. Wilcox
2016-12-14 10:53 ` Szabolcs Nagy
2016-12-15 4:11 ` A. Wilcox [this message]
2016-12-15 10:59 ` Szabolcs Nagy
2016-12-15 18:58 ` Rich Felker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=58521805.5000308@Wilcox-Tech.com \
--to=awilcox@wilcox-tech.com \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).