mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Markus Wichmann <nullplan@gmx.net>
To: musl@lists.openwall.com
Subject: Re: [musl] Posits support under Musl libc?
Date: Mon, 29 Jun 2020 20:15:40 +0200	[thread overview]
Message-ID: <20200629181540.GC13001@voyager> (raw)
In-Reply-To: <20200629162642.GI2048759@port70.net>

On Mon, Jun 29, 2020 at 06:26:42PM +0200, Szabolcs Nagy wrote:
> i would not hold my breath for posit support even if it was the
> best possible floating-point format.
>
> it has to be properly standardized and added to hw architectures.
>
> then the related software standards need to be developed (abi,
> programming language support, math library behaviour for special
> cases, printf format specifiers, etc)
>
> then the tooling support has to be added (compilers, emulators,
> softfloat libraries, etc)
>
> then we can come back and consider doing something about it in
> musl.
>
> (and even then it will take time for it to be usable in user
> code: requires widely deployed hw, protocol and file format
> updates, new algorithm designs and review of existing algorithms
> for compatibility)

In addition, Posit support is going to run into the problem that IEEE
754 implementations are readily available /right now/ and are "good
enough" for most applications. Hell, most applications don't even
require floating-point at all. The good can sometimes be the enemy of
the perfect, but here I am squarely on the side of pragmatism.

Ciao,
Markus

  reply	other threads:[~2020-06-29 18:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 12:56 mayuresh
2020-06-29 16:26 ` Szabolcs Nagy
2020-06-29 18:15   ` Markus Wichmann [this message]
2020-06-29 20:17     ` Rich Felker
2020-06-29 20:46 ` Pascal Cuoq
2020-06-30  2:57   ` Jeff Hammond
  -- strict thread matches above, loose matches on Subject: below --
2020-06-29 10:42 mayuresh
2020-06-29 12:04 ` Pascal Cuoq

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=20200629181540.GC13001@voyager \
    --to=nullplan@gmx.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).