From: Keith Packard <keithp@keithp.com>
To: Jeff Law <jeffreyalaw@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libgcc/m68k: Fixes for soft float
Date: Fri, 10 Nov 2023 17:02:57 -0800 [thread overview]
Message-ID: <87y1f5nltq.fsf@keithp.com> (raw)
In-Reply-To: <9ab8c5e2-806b-4ab2-a4cd-fcce2491e6d9@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
> 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.
Yeah, a couple of minor fixes there that I forgot to mention in the log.
> 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 for that review -- m68k assembly isn't my strongest language. The
kludge to return pointers in both d1 and a1 was a bit ugly, but seemed
like a much more robust plan than attempting to use different registers
depending on the target ABI...
The real check for these fixes was to run a fairly comprehensive C
library test suite (part of picolibc) and just iterate until I stopped
getting failures. Those tests have found so many corner cases in both
the C library, FPU emulation and compilers ...
--
-keith
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2023-11-11 1:03 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
2023-11-11 1:02 ` Keith Packard [this message]
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=87y1f5nltq.fsf@keithp.com \
--to=keithp@keithp.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.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).