From: Ramana Radhakrishnan <ramana.gcc@googlemail.com>
To: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
Richard Earnshaw <Richard.Earnshaw@arm.com>,
Alex Coplan <alex.coplan@arm.com>
Subject: Re: [Patch Arm] Fix PR 92999
Date: Thu, 10 Nov 2022 19:46:29 +0000 [thread overview]
Message-ID: <CAJA7tRbpaQGt6D_=oF+VA_uuJMPgkLf6OmvCUJNJEp-TsSWLZg@mail.gmail.com> (raw)
In-Reply-To: <b8b1d4c7-a90c-1a14-2b0e-8bcd7792f986@foss.arm.com>
On Thu, Nov 10, 2022 at 6:03 PM Richard Earnshaw
<Richard.Earnshaw@foss.arm.com> wrote:
>
>
>
> On 10/11/2022 17:21, Richard Earnshaw via Gcc-patches wrote:
> >
> >
> > On 08/11/2022 18:20, Ramana Radhakrishnan via Gcc-patches wrote:
> >> PR92999 is a case where the VFP calling convention does not allocate
> >> enough FP registers for a homogenous aggregate containing FP16 values.
> >> I believe this is the complete fix but would appreciate another set of
> >> eyes on this.
> >>
> >> Could I get a hand with a regression test run on an armhf environment
> >> while I fix my environment ?
> >>
> >> gcc/ChangeLog:
> >>
> >> PR target/92999
> >> * config/arm/arm.c (aapcs_vfp_allocate_return_reg): Adjust to handle
> >> aggregates with elements smaller than SFmode.
> >>
> >> gcc/testsuite/ChangeLog:
> >>
> >> * gcc.target/arm/pr92999.c: New test.
> >>
> >>
> >> Thanks,
> >> Ramana
> >>
> >> Signed-off-by: Ramana Radhakrishnan <ramana.gcc@gmail.com>
> >
> > I'm not sure about this. The AAPCS does not mention a base type of a
> > half-precision FP type as an appropriate homogeneous aggregate for using
> > VFP registers for either calling or returning.
Ooh interesting, thanks for taking a look and poking at the AAPCS and
that's a good catch. BF16 should also have the same behaviour as FP16
, I suspect ?
> >
> > So perhaps the bug is that we try to treat this as a homogeneous
> > aggregate at all.
Yep I agree - I'll take a look again tomorrow and see if I can get a fix.
(And thanks Alex for the test run, I might trouble you again while I
still (slowly) get some of my boards back up)
regards,
Ramana
>
> R.
next prev parent reply other threads:[~2022-11-10 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 18:20 Ramana Radhakrishnan
2022-11-09 18:42 ` Alex Coplan
2022-11-10 17:21 ` Richard Earnshaw
2022-11-10 18:03 ` Richard Earnshaw
2022-11-10 19:46 ` Ramana Radhakrishnan [this message]
2022-11-11 21:50 ` Ramana Radhakrishnan
2022-11-17 20:15 ` Ramana Radhakrishnan
2022-11-24 12:32 ` Ramana Radhakrishnan
2022-11-24 16:12 ` Richard Earnshaw
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='CAJA7tRbpaQGt6D_=oF+VA_uuJMPgkLf6OmvCUJNJEp-TsSWLZg@mail.gmail.com' \
--to=ramana.gcc@googlemail.com \
--cc=Richard.Earnshaw@arm.com \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=alex.coplan@arm.com \
--cc=gcc-patches@gcc.gnu.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).