From: Jeff Law <jeffreyalaw@gmail.com>
To: Keith Packard <keithp@keithp.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libgcc/m68k: Fixes for soft float
Date: Fri, 10 Nov 2023 16:49:48 -0700 [thread overview]
Message-ID: <9ab8c5e2-806b-4ab2-a4cd-fcce2491e6d9@gmail.com> (raw)
In-Reply-To: <20230823021504.3864764-1-keithp@keithp.com>
On 8/22/23 20:15, Keith Packard via Gcc-patches wrote:
> Check for non-zero denorm in __adddf3. Need to check both the upper and
> lower 32-bit chunks of a 64-bit float for a non-zero value when
> checking to see if the value is -0.
>
> Fix __addsf3 when the sum exponent is exactly 0xff to ensure that
> produces infinity and not nan.
>
> Handle converting NaN/inf values between formats.
>
> Handle underflow and overflow when truncating.
>
> Write a replacement for __fixxfsi so that it does not raise extra
> exceptions during an extra conversion from long double to double.
>
> Signed-off-by: Keith Packard <keithp@keithp.com>
I pushed this to the trunk after fixing a few minor whitespace nits.
You didn't mention the divdf change, but I'll assume that was just an
oversight.
I'm largely trusting your reputation on the fpgnulib changes. I won't
claim to know that code at all. The assembly bits were simple enough
that I could make out what you were doing relatively easily.
Thanks again,
Jeff
next prev parent reply other threads:[~2023-11-10 23:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 2:15 Keith Packard
2023-11-10 23:49 ` Jeff Law [this message]
2023-11-11 1:02 ` Keith Packard
2023-11-11 17:51 ` Jeff Law
2025-01-01 21:16 ` [PATCH] libgcc/m68k: More fixes " Keith Packard
2025-01-07 21:59 ` Jeff Law
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=9ab8c5e2-806b-4ab2-a4cd-fcce2491e6d9@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=keithp@keithp.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).