From: Palmer Dabbelt <palmer@dabbelt.com>
To: joseph@codesourcery.com
Cc: ludovic@rivosinc.com, libc-alpha@sourceware.org
Subject: Re: Behaviour differences on x86 and RISC-V on cos/sin functions
Date: Thu, 08 Dec 2022 12:07:58 -0800 (PST) [thread overview]
Message-ID: <mhng-9a1e81c1-1035-4b6b-bbbb-86ade9f63ce4@palmer-ri-x1c9a> (raw)
In-Reply-To: <9add23f-a02c-f5a3-298e-d0b95d52c219@codesourcery.com>
On Thu, 08 Dec 2022 12:06:59 PST (-0800), joseph@codesourcery.com wrote:
> On Thu, 8 Dec 2022, Palmer Dabbelt wrote:
>
>> So it's OK to follow the RISC-V rules for library functions? We don't have
>
> Yes (only a few functions such as fabs and copysign need to do anything in
> particular regarding NaN payloads or signs).
>
>> In other words: it's safe to call this behavior not a bug?
>
> Correct.
Thanks.
next prev parent reply other threads:[~2022-12-08 20:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 18:23 Ludovic Henry
2022-12-08 18:49 ` Joseph Myers
2022-12-08 19:24 ` Ludovic Henry
2022-12-08 19:58 ` Palmer Dabbelt
2022-12-08 20:06 ` Joseph Myers
2022-12-08 20:07 ` Palmer Dabbelt [this message]
2022-12-08 19:59 ` Joseph Myers
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=mhng-9a1e81c1-1035-4b6b-bbbb-86ade9f63ce4@palmer-ri-x1c9a \
--to=palmer@dabbelt.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=ludovic@rivosinc.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.
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).