public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: Alex Coplan <alex.coplan@arm.com>, gcc-patches@gcc.gnu.org
Cc: Marek Polacek <polacek@redhat.com>,
	Nathan Sidwell <nathan@acm.org>,
	Joseph Myers <joseph@codesourcery.com>,
	Iain Sandoe <iain@sandoe.co.uk>
Subject: Re: [PATCH v5] c-family: Implement __has_feature and __has_extension [PR60512]
Date: Mon, 20 Nov 2023 17:29:58 -0500	[thread overview]
Message-ID: <54f7dafb-e8cf-4282-a042-a4abcba6494f@redhat.com> (raw)
In-Reply-To: <ZVd9xQwlHnI8G8wQ@arm.com>

On 11/17/23 09:50, Alex Coplan wrote:
> Hi,
> 
> This is a v5 patch to address Marek's feedback here:
> https://gcc.gnu.org/pipermail/gcc-patches/2023-November/635157.html
> 
> I also implemented Jason's suggestion to use constexpr for the tables
> from this review:
> https://gcc.gnu.org/pipermail/gcc-patches/2023-October/634484.html
> 
> I'll attach the incremental change in reply to Marek's review to make
> things easier to compare.
> 
> Bootstrapped/regtested on aarch64-linux-gnu.  Bootstrap/regtest on
> x86_64-apple-darwin in progress (on top of this libsanitizer fix:
> https://github.com/llvm/llvm-project/issues/72639).
> 
> OK for trunk if testing passes?

> --- a/gcc/c-family/c-common.h
> +/* Implemented in c/c-objc-common.cc.  */
> +extern void c_register_features ();

I think this declaration should go in c-objc-common.h, though the C 
maintainers might prefer c-lang.h or c-tree.h.

> +/* Implemented in cp/cp-objcp-common.cc.  */
> +extern void cp_register_features ();

And this one in cp-objc-common.h.

With that change the patch is OK on Friday if Marek doesn't have any 
other notes.

Thanks,
Jason


  reply	other threads:[~2023-11-20 22:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17 14:50 Alex Coplan
2023-11-20 22:29 ` Jason Merrill [this message]
2023-11-23 17:41   ` Marek Polacek
2023-11-27 10:58     ` Alex Coplan
2023-11-28  8:22       ` [PATCH] c++: Fix up __has_extension (cxx_init_captures) Jakub Jelinek
2023-11-28 16:45         ` Alex Coplan
2023-11-28 17:12           ` Jakub Jelinek
2023-11-28 17:18             ` Jason Merrill
2023-11-28 17:08         ` Jason Merrill
2023-11-28 16:03 ` [PATCH v5] c-family: Implement __has_feature and __has_extension [PR60512] Thomas Schwinge
2023-11-28 16:53   ` Alex Coplan
2023-11-28 17:08   ` Jason Merrill

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=54f7dafb-e8cf-4282-a042-a4abcba6494f@redhat.com \
    --to=jason@redhat.com \
    --cc=alex.coplan@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iain@sandoe.co.uk \
    --cc=joseph@codesourcery.com \
    --cc=nathan@acm.org \
    --cc=polacek@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).