mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: test results from latest git
Date: Mon, 15 Feb 2016 22:04:52 +0100	[thread overview]
Message-ID: <20160215210452.GS9915@port70.net> (raw)
In-Reply-To: <20160215201122.GU9349@brightrain.aerifal.cx>

* Rich Felker <dalias@libc.org> [2016-02-15 15:11:22 -0500]:
> On Mon, Feb 15, 2016 at 09:05:40PM +0100, Waldemar Brodkorb wrote:
> > Hi,
> > Szabolcs Nagy wrote,
> > 
> > > * Waldemar Brodkorb <wbx@openadk.org> [2016-02-15 17:45:11 +0100]:
> > > > 
> > > > I uploaded latest test results from embedded-test here:
> > > > http://tests.embedded-test.org/musl/git-14022016/
> > > > 
> > > 
> > > hm, almost all armv7 float/math tests failed
> > > 
> > > can you give some info about the toolchain? (gcc -v)
> > > and the armv6 one for comparision? (which seems to work)
> > 
> > ARMv6:
> > usr/bin/arm-openadk-linux-musleabihf-gcc -v
> > Using built-in specs.
> > COLLECT_GCC=./openadk/toolchain_qemu-arm-realview-eb-mpcore_musl_arm_hard_eabihf/usr/bin/arm-openadk-linux-musleabihf-gcc
> > COLLECT_LTO_WRAPPER=/home/wbx/embedded-test/openadk/toolchain_qemu-arm-realview-eb-mpcore_musl_arm_hard_eabihf/usr/libexec/gcc/arm-openadk-linux-musleabihf/5.3.0/lto-wrapper
> > Target: arm-openadk-linux-musleabihf
> > Configured with:
> > /home/wbx/embedded-test/openadk/toolchain_build_qemu-arm-realview-eb-mpcore_musl_arm_hard_eabihf/w-gcc-5.3.0-1/gcc-5.3.0/configure
> > --prefix=/home/wbx/embedded-test/openadk/toolchain_qemu-arm-realview-eb-mpcore_musl_arm_hard_eabihf/usr
> > --with-bugurl=http://www.openadk.org/ --build=x86_64-linux-gnu
> > --host=x86_64-linux-gnu --target=arm-openadk-linux-musleabihf
> > --with-gmp=/home/wbx/embedded-test/openadk/host_x86_64-linux-gnu/usr
> > --with-mpfr=/home/wbx/embedded-test/openadk/host_x86_64-linux-gnu/usr
> > --with-libelf=/home/wbx/embedded-test/openadk/host_x86_64-linux-gnu/usr
> > --disable-__cxa_atexit --with-system-zlib --with-gnu-ld
> > --with-gnu-as --disable-libsanitizer --disable-install-libiberty
> > --disable-libitm --disable-libmudflap --disable-libgomp
> > --disable-libcilkrts --disable-libquadmath
> > --disable-libquadmath-support --disable-decimal-float
> > --disable-libstdcxx-pch --disable-ppl-version-check
> > --disable-cloog-version-check --without-ppl --without-cloog
> > --without-isl --disable-nls --disable-lto --with-cpu=mpcore
> > --with-float=hard --enable-tls --enable-threads --enable-libatomic
> > --enable-shared=libstdc++,libgcc --disable-libssp --disable-biarch
> > --disable-multilib --enable-cxx-flags=-fPIC --enable-languages=c,c++
> > --with-build-sysroot='/../../target_qemu-arm-realview-eb-mpcore_musl_arm_hard_eabihf'
> > --with-sysroot='/../../target_qemu-arm-realview-eb-mpcore_musl_arm_hard_eabihf'
> > Thread model: posix
> > gcc version 5.3.0 (GCC) 
> > 
> > ARMv7:
> > usr/bin/arm-openadk-linux-musleabihf-gcc -v
> > Using built-in specs.
> > COLLECT_GCC=./openadk/toolchain_qemu-arm-vexpress-a9_musl_arm_hard_eabihf/usr/bin/arm-openadk-linux-musleabihf-gcc
> > COLLECT_LTO_WRAPPER=/home/wbx/embedded-test/openadk/toolchain_qemu-arm-vexpress-a9_musl_arm_hard_eabihf/usr/libexec/gcc/arm-openadk-linux-musleabihf/5.3.0/lto-wrapper
> > Target: arm-openadk-linux-musleabihf
> > Configured with:
> > /home/wbx/embedded-test/openadk/toolchain_build_qemu-arm-vexpress-a9_musl_arm_hard_eabihf/w-gcc-5.3.0-1/gcc-5.3.0/configure
> > --prefix=/home/wbx/embedded-test/openadk/toolchain_qemu-arm-vexpress-a9_musl_arm_hard_eabihf/usr
> > --with-bugurl=http://www.openadk.org/ --build=x86_64-linux-gnu
> > --host=x86_64-linux-gnu --target=arm-openadk-linux-musleabihf
> > --with-gmp=/home/wbx/embedded-test/openadk/host_x86_64-linux-gnu/usr
> > --with-mpfr=/home/wbx/embedded-test/openadk/host_x86_64-linux-gnu/usr
> > --with-libelf=/home/wbx/embedded-test/openadk/host_x86_64-linux-gnu/usr
> > --disable-__cxa_atexit --with-system-zlib --with-gnu-ld
> > --with-gnu-as --disable-libsanitizer --disable-install-libiberty
> > --disable-libitm --disable-libmudflap --disable-libgomp
> > --disable-libcilkrts --disable-libquadmath
> > --disable-libquadmath-support --disable-decimal-float
> > --disable-libstdcxx-pch --disable-ppl-version-check
> > --disable-cloog-version-check --without-ppl --without-cloog
> > --without-isl --disable-nls --disable-lto --with-cpu=cortex-a9
> > --with-float=hard --with-fpu=neon-fp16 --enable-tls --enable-threads
> > --enable-libatomic --enable-shared=libstdc++,libgcc --disable-libssp
> > --disable-biarch --disable-multilib --enable-cxx-flags=-fPIC
> > --enable-languages=c,c++
> > --with-build-sysroot='/../../target_qemu-arm-vexpress-a9_musl_arm_hard_eabihf'
> > --with-sysroot='/../../target_qemu-arm-vexpress-a9_musl_arm_hard_eabihf'
> > Thread model: posix
> > gcc version 5.3.0 (GCC) 
> > 
> > I do not configure any --with-fpu for ARMv6. Are NEON intrinsics the
> > problem?
> 
> OK, Neon is almost certainly your problem. It should never be used as

--with-fpu=neon-fp16 should just mean that neon and 16bit fp are
available (as extensions to vfp), it does not mean neon arithmetics
is used by default (and even if it were the failures are not explained)

there is some fundamental problem with the toolchain/qemu/..
and i dont yet see what.. e.g. wrong float.h was used or
similarly bad thing.

> the default for a toolchain because it produces non-IEEE-conforming
> results. You can enable Neon for individual applications where you
> don't care (just like -ffast-math) but using it to build libc will
> result in a broken libc, and using it by default could break other
> apps too. Perhaps we should add something to musl's configure to
> detect this misconfiguration and error out or disable Neon?
> 
> Rich


  reply	other threads:[~2016-02-15 21:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15 16:45 Waldemar Brodkorb
2016-02-15 19:25 ` Szabolcs Nagy
2016-02-15 20:05   ` Waldemar Brodkorb
2016-02-15 20:11     ` Rich Felker
2016-02-15 21:04       ` Szabolcs Nagy [this message]
2016-02-15 21:32         ` Szabolcs Nagy
2016-02-16 18:07           ` Waldemar Brodkorb
2016-02-16 20:00             ` Szabolcs Nagy
2016-02-16 20:13             ` 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=20160215210452.GS9915@port70.net \
    --to=nsz@port70.net \
    --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).