public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* [PATCH] alpha: Fix alpha_setup_incoming_varargs [PR114175]
@ 2024-03-18 18:40 Jakub Jelinek
  2024-03-19  3:06 ` Jeff Law
  0 siblings, 1 reply; 2+ messages in thread
From: Jakub Jelinek @ 2024-03-18 18:40 UTC (permalink / raw)
  To: Uros Bizjak, Richard Henderson; +Cc: gcc-patches

Hi!

Like in the r14-9503 change on x86-64, I think Alpha also needs to
function_arg_advance after the hidden return pointer argument if
any.
At least, the following patch changes the assembly of s1-s6 functions
on the https://gcc.gnu.org/pipermail/gcc-patches/2024-March/647956.html
c23-stdarg-9.c testcase, and eyeballing the assembly for int f8 (...)
the ... args are passed in 16..21 registers and then on the stack,
while for struct S s8 (...) have hidden return pointer passed in 16
register and ... args in 17..21 registers and then on the stack, and
seems without this patch the incoming varargs setup does the wrong thing
(but I can't test on alpha easily).

Many targets seem to be unaffected, e.g. aarch64, arm, s390*, so I'm not
trying to change all targets together because such a change clearly isn't
needed e.g. for targets which use special register for the hidden return
pointer.

Ok for trunk?

2024-03-18  Jakub Jelinek  <jakub@redhat.com>

	PR target/114175
	* config/alpha/alpha.cc (alpha_setup_incoming_varargs): Only skip
	function_arg_advance for TYPE_NO_NAMED_ARGS_STDARG_P functions
	if arg.type is NULL.

--- gcc/config/alpha/alpha.cc.jj	2024-01-05 15:22:21.762686175 +0100
+++ gcc/config/alpha/alpha.cc	2024-03-18 16:12:14.594761619 +0100
@@ -6090,7 +6090,8 @@ alpha_setup_incoming_varargs (cumulative
 {
   CUMULATIVE_ARGS cum = *get_cumulative_args (pcum);
 
-  if (!TYPE_NO_NAMED_ARGS_STDARG_P (TREE_TYPE (current_function_decl)))
+  if (!TYPE_NO_NAMED_ARGS_STDARG_P (TREE_TYPE (current_function_decl))
+      || arg.type != NULL_TREE)
     /* Skip the current argument.  */
     targetm.calls.function_arg_advance (pack_cumulative_args (&cum), arg);
 

	Jakub


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PATCH] alpha: Fix alpha_setup_incoming_varargs [PR114175]
  2024-03-18 18:40 [PATCH] alpha: Fix alpha_setup_incoming_varargs [PR114175] Jakub Jelinek
@ 2024-03-19  3:06 ` Jeff Law
  0 siblings, 0 replies; 2+ messages in thread
From: Jeff Law @ 2024-03-19  3:06 UTC (permalink / raw)
  To: gcc-patches



On 3/18/24 12:40 PM, Jakub Jelinek wrote:
> Hi!
> 
> Like in the r14-9503 change on x86-64, I think Alpha also needs to
> function_arg_advance after the hidden return pointer argument if
> any.
> At least, the following patch changes the assembly of s1-s6 functions
> on the https://gcc.gnu.org/pipermail/gcc-patches/2024-March/647956.html
> c23-stdarg-9.c testcase, and eyeballing the assembly for int f8 (...)
> the ... args are passed in 16..21 registers and then on the stack,
> while for struct S s8 (...) have hidden return pointer passed in 16
> register and ... args in 17..21 registers and then on the stack, and
> seems without this patch the incoming varargs setup does the wrong thing
> (but I can't test on alpha easily).
> 
> Many targets seem to be unaffected, e.g. aarch64, arm, s390*, so I'm not
> trying to change all targets together because such a change clearly isn't
> needed e.g. for targets which use special register for the hidden return
> pointer.
> 
> Ok for trunk?
> 
> 2024-03-18  Jakub Jelinek  <jakub@redhat.com>
> 
> 	PR target/114175
> 	* config/alpha/alpha.cc (alpha_setup_incoming_varargs): Only skip
> 	function_arg_advance for TYPE_NO_NAMED_ARGS_STDARG_P functions
> 	if arg.type is NULL.
OK.  And I think you should go ahead with any others that you think need 
a similar change.  I certainly trust your judgment.

jeff

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2024-03-19  3:06 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-03-18 18:40 [PATCH] alpha: Fix alpha_setup_incoming_varargs [PR114175] Jakub Jelinek
2024-03-19  3:06 ` Jeff Law

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).