[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0e84ee33-dc3a-b986-dd16-955ca3cd37fb@mirbsd.de>
Date: Sat, 8 Mar 2025 13:41:29 +0100 (CET)
From: Thorsten Glaser <tg@...bsd.de>
To: musl@...ts.openwall.com
Subject: Re: f128 aliases for long double math symbols
On Fri, 7 Mar 2025, Rich Felker wrote:
>because we demand analyzability and compatibility with type checking
>tooling and, on a more abstract level, because we demand that the C in
>musl be valid freestanding C that may depend on particular
>implementation-defined behaviors and a small set of extensions, but
>not on undefined behavior. This is a choice.
[…]
>I don't think it's an allowance that I'd like to make use of, and I
OK.
Mostly we were discussing this because you made it sound like it’s
not permitted for any implementation to do that, or for application
code to rely on implementations not doing that.
A choice, for musl, is fine (and while I don’t agree with all the
choices, you have my respect anyway).
bye,
//mirabilos
--
“It is inappropriate to require that a time represented as
seconds since the Epoch precisely represent the number of
seconds between the referenced time and the Epoch.”
-- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
