public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Newlib <newlib@sourceware.org>
Subject: fenv soft-float support
Date: Tue, 14 Jul 2020 10:00:54 +0200	[thread overview]
Message-ID: <5281ca5f-527b-20ec-62e8-118a157d1219@embedded-brains.de> (raw)

Hello,

the recent fenv patches added support for the soft-float implementation 
of FreeBSD. Newlib uses the one from libgcc by default. They are not 
compatible. Having an GCC incompatible soft-float fenv support in Newlib 
makes no sense to me.

How can we fix this?

As a short-term fix, I would remove the FreeBSD fenv support. What 
should we provide instead? I would just provide the hardware 
implementation of the architecture for now. If someone uses this in a 
soft-float configuration, he may get exceptions or some sort of 
undefined behaviour. This is what you get on powerpc currently.

A long-term solution would be to add support for the GCC soft-float 
implementation in libgcc. This requires changes in the GCC 
configuration. I guess this is a bit of work.



                 reply	other threads:[~2020-07-14  8:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5281ca5f-527b-20ec-62e8-118a157d1219@embedded-brains.de \
    --to=sebastian.huber@embedded-brains.de \
    --cc=newlib@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).