Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Question about float-abi
Date: Wed, 29 Feb 2012 15:47:10 +0100	[thread overview]
Message-ID: <20120229154710.7729776d@skate> (raw)
In-Reply-To: <20120229134909.GO23707@ldesroches-Latitude-E6320>

Hello Ludovic,

Le Wed, 29 Feb 2012 14:49:09 +0100,
Ludovic Desroches <ludovic.desroches@atmel.com> a ?crit :

> Yes there were missing options for gcc: --with-float=hard and
> --with-fpu=...
> 
> Now floating score is correct. I am surprised by the good results of
> the uclibc. I don't know if nbench is an accurate benchmark to test
> several libc but scores obtained by glibc, eglibc and uclibc are very
> closed.

As I told you on IRC, those investigations are really interesting. We
know that the Buildroot support for floating-point is far from perfect,
this has been briefly discussed during the last Buildroot Developer
meeting. If you want to improve this part of Buildroot, do not hesitate
to send patches, we are definitely interested.

I guess with internal toolchains, it's quite easy to improve things.
The case of external toolchains is probably a bit more complicated,
since we do not control how the C library of the external toolchain has
been built in terms of floating point support.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-02-29 14:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 10:55 [Buildroot] Question about float-abi Ludovic Desroches
2012-02-29 11:08 ` Ludovic Desroches
2012-02-29 13:49   ` Ludovic Desroches
2012-02-29 14:47     ` Thomas Petazzoni [this message]
2012-03-01  8:09       ` Ludovic Desroches

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=20120229154710.7729776d@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox