public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [committed] ft32: Fix up ft32_setup_incoming_varargs [PR114175]
Date: Wed, 20 Mar 2024 11:01:06 -0600	[thread overview]
Message-ID: <dd275ea0-53e6-4748-aeae-d6cc62e75069@gmail.com> (raw)
In-Reply-To: <ZfsJVt4JH3K3CFHv@tucnak>



On 3/20/24 10:05 AM, Jakub Jelinek wrote:
> Hi!
> 
> Like for x86-64, alpha or rs6000, ft32 seems to be affected too.
> 
> Just visually checked differences in c23-stdarg-9.c assembly in a cross
> without/with the patch, committed to trunk.
> 
> 2024-03-20  Jakub Jelinek  <jakub@redhat.com>
> 
> 	PR target/114175
> 	* config/ft32/ft32.cc (ft32_setup_incoming_varargs): Only skip
> 	function arg advance for TYPE_NO_NAMED_ARGS_STDARG_P functions
> 	if arg.type is NULL.
Built fine.  No gdbsim on this platform, so no execution test data.

jeff


      reply	other threads:[~2024-03-20 17:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20 16:05 Jakub Jelinek
2024-03-20 17:01 ` Jeff Law [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=dd275ea0-53e6-4748-aeae-d6cc62e75069@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.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).