public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: Patch ping: Re: [PATCH] c, c++, v2: Accept __builtin_classify_type (typename)
Date: Mon, 18 Sep 2023 21:25:19 +0000	[thread overview]
Message-ID: <3c117643-59c-8cd7-f6a6-3663fb524dde@codesourcery.com> (raw)
In-Reply-To: <ZQgbi9gWOXcRatqc@tucnak>

On Mon, 18 Sep 2023, Jakub Jelinek via Gcc-patches wrote:

> Hi!
> 
> I'd like to ping this patch.
> The C++ FE part has been approved by Jason already with a minor change
> I've made in my copy.
> Are the remaining parts ok for trunk?

In the C front-end changes, since you end up discarding any side effects 
from the type, I'd expect use of in_alignof to be more appropriate than 
in_typeof (and thus not needing to use pop_maybe_used).

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2023-09-18 21:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 19:57 [PATCH] c, c++: " Jakub Jelinek
2023-06-13  8:48 ` Jason Merrill
2023-08-10 15:35 ` [PATCH] c, c++, v2: " Jakub Jelinek
2023-08-10 21:44   ` Jason Merrill
2023-08-10 22:27     ` Joseph Myers
2023-08-10 23:13     ` Jakub Jelinek
2023-08-11  8:48       ` Jakub Jelinek
2023-08-11 16:12         ` Jason Merrill
2023-09-18  9:42         ` Patch ping: " Jakub Jelinek
2023-09-18 21:25           ` Joseph Myers [this message]
2023-09-20  7:17             ` [PATCH] c, c++, v3: " Jakub Jelinek
2023-09-20 16:08               ` Joseph Myers

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=3c117643-59c-8cd7-f6a6-3663fb524dde@codesourcery.com \
    --to=joseph@codesourcery.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).