From: "mayuresh@kathe.in" <mayuresh@kathe.in>
To: musl@lists.openwall.com
Subject: Re: [musl] Posits support under Musl libc?
Date: Mon, 29 Jun 2020 14:56:09 +0200 [thread overview]
Message-ID: <32b4-5ef9e500-33-6d961680@199533904> (raw)
On Monday, June 29, 2020 05:34 PM IST, Pascal Cuoq <cuoq@trust-in-soft.com> wrote:
> > Can the "musl" libc project consider supporting the Posit number format in the math routines?
>
> > More details;
> > https://posithub.org/docs/Posits4.pdf
> > https://posithub.org/docs/BeatingFloatingPoint.pdf
>
> > And a sample implementation;
> > https://gitlab.com/cerlane/SoftPosit
>
> I am not a musl contributor and have no say in what it should contain or not, but why in hell a software implementation of a non-standard floating-point format that only its inventor seems to think has any concrete advantage over IEEE 754 belong in a libc the goals of which are below?
>
> “lightweight, fast, simple, free, and strives to be correct in the sense of standards-conformance and safety.” (from https://musl.libc.org/ )
>
> Posits are 1 out of 5 (I think they are free).
Posits are lightweight, fast, free and produce the same results across platforms, something which IEEE 754 doesn't guarantee. To top that, IEEE 754 isn't even a standard but just a set of guidelines which are usually implemented incorrectly due to misinterpretation or lack of expertise. So in that sense, Posits are safer than Floating-point.
That makes Posits, 4 out of 5 (which seems a much better proposition).
~Mayuresh
next reply other threads:[~2020-06-29 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 12:56 mayuresh [this message]
2020-06-29 16:26 ` Szabolcs Nagy
2020-06-29 18:15 ` Markus Wichmann
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=32b4-5ef9e500-33-6d961680@199533904 \
--to=mayuresh@kathe.in \
--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).