public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/102148] ppc64le: homogeneous float arguments are not passed correctly
Date: Wed, 01 Sep 2021 20:18:18 +0000	[thread overview]
Message-ID: <bug-102148-4-sUX8yAfpmY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102148-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102148

--- Comment #5 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
For anyone running into this problem and wondering about the resolution:

It is a matter of some confusion how homogeneous aggregates are mapped to the
parameter save area. This came up recently with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102148. It would be helpful to add
some clarifying text for the following points.

(1) The parameter save area layout is completely independent from the rules for
passing homogeneous aggregates in registers.
(2) The size of a homogeneous aggregate parameter in the parameter save area is
the size of that aggregate by normal rules of alignment and padding. This means
that the parameter save area for a homogeneous aggregate of 32-bit floats takes
up less room than the amount of register space consumed.
(3) The number of GPRs skipped is based upon the size of the aggregate in the
parameter save area.

An example of this exists (Figure 2.26 in revision 1.5), but it is easy to have
difficulty spotting the information there.

      parent reply	other threads:[~2021-09-01 20:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31 18:29 [Bug c/102148] New: " zlwang at ca dot ibm.com
2021-09-01 15:13 ` [Bug target/102148] " dje at gcc dot gnu.org
2021-09-01 20:00 ` zlwang at ca dot ibm.com
2021-09-01 20:03 ` zlwang at ca dot ibm.com
2021-09-01 20:04 ` wschmidt at gcc dot gnu.org
2021-09-01 20:18 ` wschmidt at gcc dot gnu.org [this message]

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=bug-102148-4-sUX8yAfpmY@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).