From: ardi <ardillasdelmonte@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Views on bare metal port
Date: Sun, 1 Apr 2018 22:12:32 +0200 [thread overview]
Message-ID: <CA+fZqCU-1gBMhiLD9WkfDhoHr95ckSxA_mM0rxRhZi0PEbin8Q@mail.gmail.com> (raw)
In-Reply-To: <20180401142905.GF4418@port70.net>
On Sun, Apr 1, 2018 at 4:29 PM, Szabolcs Nagy <nsz@port70.net> wrote:
> in short:
>
> most things will work even if musl is compiled by a
> compiler without fenv access support, but it won't
> be fully conforming when the caller changes or tests
> the fenv.
Thanks a lot for your detailed clarifications! I never change the
rounding mode in my code, nor use the functions you mention, so I
think I'm safe to use clang with musl.
BTW, am I correct in assuming that these clang rounding mode issues
happen in all C runtimes in all OSs (MacOS included), or do some C
runtimes apply some hacks for preventing this behaviour? I feel a bit
puzzled about MacOS not saying a word about this in the docs. For
example, the MacOS manpages for fesetround() and for the functions you
mention, don't say a word about possible undesired behaviour with
clang.
Thanks!
ardi
next prev parent reply other threads:[~2018-04-01 20:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOUYtQBwKmfwjmxUy+mfd0Qg+n78rCwKtK2=X6xgK-Cmt6EGXQ@mail.gmail.com>
[not found] ` <CAOUYtQB4+8Yey+Q2yT3GWqTiobgPNf60G6dZHjUyjbj1SUC0TA@mail.gmail.com>
[not found] ` <CAOUYtQD1LF03fbZ3U4e=s3uXiiY46jkuTjvzdfnz=c3mvzCrhw@mail.gmail.com>
[not found] ` <CAOUYtQAZ-90b39f0Okz+KsnYK9G1FwdpTGtMSwJsWtsPwEWM-Q@mail.gmail.com>
[not found] ` <CAOUYtQCNCU4rN74+HHmBTfgLTEdAhypWSL1L=Ooc1ocqjpEW_Q@mail.gmail.com>
[not found] ` <CAOUYtQCCwhp-RSmod+dzLrFzqrR_Om-p6dD5kEkNtMT2B48FjQ@mail.gmail.com>
[not found] ` <CAOUYtQDM4BW=WEXD5RK2YWf+3zj+opBuK8vsPwEPfyM3Hyo_6w@mail.gmail.com>
[not found] ` <CAOUYtQCsJU_qczmjpH8NHbgqSHVLEAYOdpHVu7nmkie3zWAAyw@mail.gmail.com>
[not found] ` <CAOUYtQDc8VHkH13Ah_+azk+goeOsthjFOhE4KfV6PCMoMKfukA@mail.gmail.com>
[not found] ` <CAOUYtQCJD1Y-xV2bbBiGxE-W8jSWA9Qm=bzn1ri5Lq9+ACKSLw@mail.gmail.com>
[not found] ` <CAOUYtQA3i8-z+LtzDbsUTJmLn76UXvDUpbKVHNfECSCMrPdiKA@mail.gmail.com>
[not found] ` <CAOUYtQBDV0_0hkjtT3A+uOqnDkuKD-ZDr_DLo=DVSO5B6YZ3AA@mail.gmail.com>
[not found] ` <CAOUYtQCHi6qR+=Jae--6M1VzeSiDBjj9_86hkpmN=XhSFDTTiQ@mail.gmail.com>
2018-01-31 13:38 ` Jon Chesterfield
2018-01-31 15:25 ` Rich Felker
2018-01-31 17:51 ` Jon Chesterfield
2018-01-31 18:25 ` Szabolcs Nagy
2018-01-31 18:37 ` Jon Chesterfield
2018-01-31 19:11 ` Rich Felker
2018-04-01 11:19 ` ardi
2018-04-01 14:29 ` Szabolcs Nagy
2018-04-01 20:12 ` ardi [this message]
2018-02-17 22:37 ` ardi
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=CA+fZqCU-1gBMhiLD9WkfDhoHr95ckSxA_mM0rxRhZi0PEbin8Q@mail.gmail.com \
--to=ardillasdelmonte@gmail.com \
--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).