From: Jakub Jelinek <jakub@redhat.com>
To: Alexandre Oliva <oliva@adacore.com>
Cc: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,
Matthew Malcomson <matthew.malcomson@arm.com>,
gcc-patches@gcc.gnu.org, Joseph Myers <josmyers@redhat.com>,
Nick Clifton <nickc@redhat.com>,
Ramana Radhakrishnan <ramana.gcc@gmail.com>,
Kyrylo Tkachov <kyrylo.tkachov@arm.com>
Subject: Re: [PATCH] arm: fix c23 0-named-args caller-side stdarg
Date: Wed, 6 Mar 2024 21:32:56 +0100 [thread overview]
Message-ID: <ZejS+POIs2Nggv3+@tucnak> (raw)
In-Reply-To: <or8r2vgl5m.fsf@lxoliva.fsfla.org>
On Wed, Mar 06, 2024 at 05:28:21PM -0300, Alexandre Oliva wrote:
> On Mar 1, 2024, "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com> wrote:
>
> > On 01/03/2024 04:38, Alexandre Oliva wrote:
> >> Thanks for the review.
>
> > For closure, Jakub has just pushed a patch to the generic code, so I
> > don't think we need this now.
>
> ACK. I see the c2x-stdarg-4.c test is now passing in our arm-eabi
> gcc-13 tree. Thank you all.
>
> Alas, the same nightly build showed a new riscv fail in c23-stdarg-6.c,
> that also got backported to gcc-13. Presumably it's failing in the
> trunk as well, both riscv32-elf and riscv64-elf.
That is PR114175 I guess. The test just makes it clear what has been broken
already in GCC 13 there.
Jakub
next prev parent reply other threads:[~2024-03-06 20:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 7:32 Alexandre Oliva
2023-12-06 2:27 ` Alexandre Oliva
2024-01-23 8:26 ` Alexandre Oliva
2024-02-26 16:41 ` Matthew Malcomson
2024-03-01 4:38 ` Alexandre Oliva
2024-03-01 14:56 ` Richard Earnshaw (lists)
2024-03-06 20:28 ` Alexandre Oliva
2024-03-06 20:32 ` Jakub Jelinek [this message]
2024-03-07 10:01 ` Richard Earnshaw (lists)
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=ZejS+POIs2Nggv3+@tucnak \
--to=jakub@redhat.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=josmyers@redhat.com \
--cc=kyrylo.tkachov@arm.com \
--cc=matthew.malcomson@arm.com \
--cc=nickc@redhat.com \
--cc=oliva@adacore.com \
--cc=ramana.gcc@gmail.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).