From: Jeff Law <jeffreyalaw@gmail.com>
To: Sam James <sam@gentoo.org>, John David Anglin <dave.anglin@bell.net>
Cc: John David Anglin <dave@parisc-linux.org>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [committed] hppa: Revise REG+D address support to allow long displacements before reload
Date: Thu, 16 Nov 2023 20:00:40 -0700 [thread overview]
Message-ID: <4d8dae42-cfe9-42a7-8c4d-1f1cbb82370f@gmail.com> (raw)
In-Reply-To: <871qcpmawz.fsf@gentoo.org>
On 11/16/23 18:20, Sam James wrote:
>
> Jeff, I don't suppose you could dig out the old bugs/commits just out of
> interest?
That work goes back to the early 90s when I was primarily responsible
for the PA platform. But the core issue hasn't changed in that not
enough context is provided for reload to know how to deal with these
problems.
So, digging out those testcases/codes would be quite difficult; at the
time we didn't have standard procedures where tests were added to the
testsuite for most changes or even discussed.
>
>> I'm not seeing any obvious problems in the gcc testsuite. It needs testing on packages that do extensive
>> floating point calculations.
>
> OK, I'll focus on those.
THe more likely scenario is xmpy which is used for integer multiply, but
the operands have to be moved into FP registers because the operation
happens in the FPU.
jeff
next prev parent reply other threads:[~2023-11-17 3:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 17:54 John David Anglin
2023-11-16 21:52 ` Jeff Law
2023-11-16 22:33 ` John David Anglin
2023-11-17 1:20 ` Sam James
2023-11-17 1:25 ` Sam James
2023-11-17 3:00 ` Jeff Law [this message]
2023-11-17 8:27 ` John David Anglin
2023-11-17 14:14 ` 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=4d8dae42-cfe9-42a7-8c4d-1f1cbb82370f@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=dave.anglin@bell.net \
--cc=dave@parisc-linux.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=sam@gentoo.org \
/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).