From: Alexandre Oliva <oliva@gnu.org>
To: Richard Earnshaw <Richard.Earnshaw@arm.com>
Cc: "Jakub Jelinek" <jakub@redhat.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
"Richard Biener" <rguenther@suse.de>,
"Jeff Law" <jeffreyalaw@gmail.com>,
gcc-patches@gcc.gnu.org,
"Torbjörn SVENSSON" <torbjorn.svensson@foss.st.com>,
"Matthew Malcomson" <matthew.malcomson@arm.com>
Subject: Re: [PATCH] calls: Fix up TYPE_NO_NAMED_ARGS_STDARG_P handling [PR107453]
Date: Fri, 01 Mar 2024 01:53:54 -0300 [thread overview]
Message-ID: <orv866imcd.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <45ac2d54-21df-486c-a085-0a6c1f37a323@arm.com> (Richard Earnshaw's message of "Tue, 27 Feb 2024 16:41:32 +0000")
On Feb 27, 2024, Richard Earnshaw <Richard.Earnshaw@arm.com> wrote:
> This one has been festering for a while; both Alexandre and Torbjorn
> have attempted to fix it recently, but I'm not sure either is really
> right...
*nod* xref https://gcc.gnu.org/pipermail/gcc-patches/2024-March/646926.html
The patch I proposed was indeed far too limited in scope.
> On Arm this is causing all anonymous arguments to be passed on the
> stack, which is incorrect per the ABI. On a target that uses
> 'pretend_outgoing_vararg_named', why is it correct to set n_named_args
> to zero? Is it enough to guard both the statements you've added with
> !targetm.calls.pretend_outgoing_args_named?
ISTM that the change you suggest over Jakub's patch would address the
inconsistency on ARM.
Matthew suggested a patch along these lines in the other thread, that I
xrefed above, that seems sound to me, but I also suspect it won't fix
the ppc64le issue. My hunch is that we'll need a combination of both,
possibly with further tweaks to adjust for Jakub's just-added test.
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice but
very few check the facts. Think Assange & Stallman. The empires strike back
next prev parent reply other threads:[~2024-03-01 4:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 10:32 Jakub Jelinek
2023-01-09 11:58 ` Richard Biener
2024-02-27 16:41 ` Richard Earnshaw
2024-02-27 17:25 ` Richard Earnshaw
2024-02-27 17:25 ` Jakub Jelinek
2024-02-27 17:54 ` Jakub Jelinek
2024-02-28 8:31 ` Jakub Jelinek
2024-02-29 14:10 ` Richard Earnshaw (lists)
2024-02-29 14:14 ` Richard Earnshaw
2024-02-29 15:55 ` [PATCH] calls: Further fixes for " Jakub Jelinek
2024-02-29 17:23 ` Richard Earnshaw (lists)
2024-02-29 17:38 ` Jakub Jelinek
2024-02-29 17:51 ` Richard Earnshaw (lists)
2024-02-29 17:56 ` Jakub Jelinek
2024-03-01 13:53 ` Richard Earnshaw (lists)
2024-03-01 14:00 ` Jakub Jelinek
2024-03-01 14:16 ` Richard Earnshaw (lists)
2024-03-01 4:53 ` Alexandre Oliva [this message]
2024-03-01 7:53 ` [PATCH] calls: Fix up " Jakub Jelinek
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=orv866imcd.fsf@lxoliva.fsfla.org \
--to=oliva@gnu.org \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jeffreyalaw@gmail.com \
--cc=joseph@codesourcery.com \
--cc=matthew.malcomson@arm.com \
--cc=rguenther@suse.de \
--cc=torbjorn.svensson@foss.st.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).