public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Paul Zimmermann <Paul.Zimmermann@inria.fr>
To: joel@rtems.org
Cc: newlib@sourceware.org, christoph.lauter@christoph-lauter.org,
	sibid@uvic.ca, Jean-Michel.Muller@ens-lyon.fr
Subject: Re: correctly rounded mathematical functions
Date: Tue, 04 Jan 2022 16:44:54 +0100	[thread overview]
Message-ID: <mw5yqzo689.fsf@tomate.loria.fr> (raw)
In-Reply-To: <CAF9ehCU9V6Z0P9Vuz7E8JKV=zNRScPs2Li5LmX1ajqUZQxDydw@mail.gmail.com> (message from Joel Sherrill on Tue, 4 Jan 2022 09:23:01 -0600)

       Hi Joel,

> How is binary128 implemented on target CPUs without native support?
> Is this something GCC will include soft methods for?

we use the _Float128 type. For internal computations we avoid it as much as
possible, using integer types, which yields a speedup of up to 10 with respect
to the glibc code.

> I didn't expect anything too fancy. Will they compile with -std=c99, c11? newlib
> generally provides all methods but the header file guards protect the prototype
> visibility.

I'll check if the code compiles with -std=c99, c11.

Best regards,
Paul

  reply	other threads:[~2022-01-04 15:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-03 12:57 Paul Zimmermann
2022-01-03 20:41 ` Joel Sherrill
2022-01-04  9:44   ` Paul Zimmermann
2022-01-04 15:23     ` Joel Sherrill
2022-01-04 15:44       ` Paul Zimmermann [this message]
2022-01-04 18:01       ` Jeff Johnston
2022-01-05 10:33         ` Paul Zimmermann
2022-01-04 18:50       ` Keith Packard
2022-01-05 11:39         ` Paul Zimmermann
2022-01-05 19:00           ` Joel Sherrill
2022-01-06 10:12             ` Paul Zimmermann
2022-01-06 14:51               ` Joel Sherrill
2022-01-06 15:33                 ` Paul Zimmermann
2022-01-05 19:43           ` Keith Packard

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=mw5yqzo689.fsf@tomate.loria.fr \
    --to=paul.zimmermann@inria.fr \
    --cc=Jean-Michel.Muller@ens-lyon.fr \
    --cc=christoph.lauter@christoph-lauter.org \
    --cc=joel@rtems.org \
    --cc=newlib@sourceware.org \
    --cc=sibid@uvic.ca \
    /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).