public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114175] [13/14] Execution test failures on gcc.dg/c23-stdarg-6.c on multiple targets
Date: Sat, 30 Mar 2024 03:54:29 +0000	[thread overview]
Message-ID: <bug-114175-4-safWoXQmeV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114175-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #51 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:d3faceaa7a18657cc73dff1405a54834e390624b

commit r13-8510-gd3faceaa7a18657cc73dff1405a54834e390624b
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Tue Mar 19 09:14:11 2024 +0100

    alpha: Fix alpha_setup_incoming_varargs [PR114175]

    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.

    2024-03-19  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.

    (cherry picked from commit a185d8aeeed7a25a01505565aa61ccf8a876c6ff)

  parent reply	other threads:[~2024-03-30  3:54 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 17:45 [Bug target/114175] New: [14] RISC-V: Execution tests on gcc.dg/c23-stdarg-6.c ewlu at rivosinc dot com
2024-02-29 17:51 ` [Bug target/114175] [14] RISC-V: Execution test failures " jakub at gcc dot gnu.org
2024-02-29 18:49 ` ewlu at rivosinc dot com
2024-02-29 18:53 ` jakub at gcc dot gnu.org
2024-02-29 18:57 ` ewlu at rivosinc dot com
2024-02-29 18:59 ` jakub at gcc dot gnu.org
2024-02-29 19:01 ` jakub at gcc dot gnu.org
2024-02-29 19:56 ` [Bug target/114175] [13/14] " jakub at gcc dot gnu.org
2024-02-29 20:03 ` jakub at gcc dot gnu.org
2024-02-29 20:07 ` palmer at gcc dot gnu.org
2024-02-29 20:09 ` jakub at gcc dot gnu.org
2024-02-29 20:09 ` jakub at gcc dot gnu.org
2024-02-29 20:20 ` jakub at gcc dot gnu.org
2024-02-29 20:22 ` jakub at gcc dot gnu.org
2024-02-29 21:28 ` palmer at gcc dot gnu.org
2024-02-29 22:20 ` palmer at gcc dot gnu.org
2024-02-29 22:46 ` ewlu at rivosinc dot com
2024-02-29 23:33 ` palmer at gcc dot gnu.org
2024-02-29 23:58 ` palmer at gcc dot gnu.org
2024-03-11 23:32 ` ewlu at rivosinc dot com
2024-03-13  2:30 ` xry111 at gcc dot gnu.org
2024-03-13  2:32 ` sjames at gcc dot gnu.org
2024-03-13  2:34 ` xry111 at gcc dot gnu.org
2024-03-15 21:46 ` sjames at gcc dot gnu.org
2024-03-15 23:10 ` jakub at gcc dot gnu.org
2024-03-16 14:17 ` cvs-commit at gcc dot gnu.org
2024-03-17 10:54 ` xry111 at gcc dot gnu.org
2024-03-18 10:16 ` [Bug target/114175] [13/14] Execution test failures on gcc.dg/c23-stdarg-6.c on multiple targets jakub at gcc dot gnu.org
2024-03-18 10:18 ` xry111 at gcc dot gnu.org
2024-03-18 10:54 ` jakub at gcc dot gnu.org
2024-03-18 11:37 ` jakub at gcc dot gnu.org
2024-03-18 12:16 ` jakub at gcc dot gnu.org
2024-03-18 18:56 ` ewlu at rivosinc dot com
2024-03-19  8:15 ` cvs-commit at gcc dot gnu.org
2024-03-19  8:15 ` cvs-commit at gcc dot gnu.org
2024-03-19  8:38 ` cvs-commit at gcc dot gnu.org
2024-03-19  8:45 ` xry111 at gcc dot gnu.org
2024-03-19  8:51 ` cvs-commit at gcc dot gnu.org
2024-03-19  8:53 ` jakub at gcc dot gnu.org
2024-03-19 16:56 ` cvs-commit at gcc dot gnu.org
2024-03-20  7:13 ` xry111 at gcc dot gnu.org
2024-03-20 16:01 ` cvs-commit at gcc dot gnu.org
2024-03-20 16:01 ` cvs-commit at gcc dot gnu.org
2024-03-20 16:01 ` cvs-commit at gcc dot gnu.org
2024-03-20 16:01 ` cvs-commit at gcc dot gnu.org
2024-03-20 16:02 ` cvs-commit at gcc dot gnu.org
2024-03-20 16:02 ` cvs-commit at gcc dot gnu.org
2024-03-20 16:02 ` cvs-commit at gcc dot gnu.org
2024-03-30  2:14 ` cvs-commit at gcc dot gnu.org
2024-03-30  3:54 ` cvs-commit at gcc dot gnu.org
2024-03-30  3:54 ` cvs-commit at gcc dot gnu.org
2024-03-30  3:54 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-30  3:54 ` cvs-commit at gcc dot gnu.org
2024-03-30  3:54 ` cvs-commit at gcc dot gnu.org
2024-03-30  3:54 ` cvs-commit at gcc dot gnu.org
2024-03-30  3:54 ` cvs-commit at gcc dot gnu.org
2024-03-30  3:55 ` cvs-commit at gcc dot gnu.org
2024-03-30  3:55 ` cvs-commit at gcc dot gnu.org
2024-03-30  3:55 ` cvs-commit at gcc dot gnu.org
2024-03-30  3:55 ` cvs-commit at gcc dot gnu.org
2024-03-30  5:49 ` cvs-commit at gcc dot gnu.org
2024-03-30  5:49 ` cvs-commit at gcc dot gnu.org
2024-04-04 16:26 ` cvs-commit at gcc dot gnu.org

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-114175-4-safWoXQmeV@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).