From: Jason Merrill <jason@redhat.com>
To: Alex Coplan <alex.coplan@arm.com>, gcc-patches@gcc.gnu.org
Cc: Nathan Sidwell <nathan@acm.org>,
Joseph Myers <joseph@codesourcery.com>,
Iain Sandoe <iain@sandoe.co.uk>
Subject: Re: [PATCH v4] c-family: Implement __has_feature and __has_extension [PR60512]
Date: Thu, 26 Oct 2023 17:06:28 -0400 [thread overview]
Message-ID: <6237945a-9b6a-45a0-94d2-8f150e4e3797@redhat.com> (raw)
In-Reply-To: <ZTjt5QERQCnciqcB@arm.com>
On 10/25/23 06:28, Alex Coplan wrote:
> On 11/10/2023 14:31, Alex Coplan wrote:
>> On 27/09/2023 15:27, Alex Coplan wrote:
>>> Hi,
>>>
>>> This is a v4 patch to address Jason's feedback here:
>>> https://gcc.gnu.org/pipermail/gcc-patches/2023-September/630911.html
>>>
>>> w.r.t. v3 it just removes a comment now that some uncertainty around
>>> cxx_binary_literals has been resolved, and updates the documentation as
>>> suggested to point to the Clang docs.
>>>
>>> ----------------------------------------------------------------------
Incidentally, putting a 8< or >8 in the line of dashes lets git am
--scissors prune the text above the line.
>>> This patch implements clang's __has_feature and __has_extension in GCC.
>>> Currently the patch aims to implement all documented features (and some
>>> undocumented ones) following the documentation at
>>> https://clang.llvm.org/docs/LanguageExtensions.html with the exception
>>> of the legacy features for C++ type traits. These are omitted, since as
>>> the clang documentation notes, __has_builtin is the correct "modern" way
>>> to query for these (which GCC already implements).
>>
>> Gentle ping on this:
>> https://gcc.gnu.org/pipermail/gcc-patches/2023-September/631525.html
>
> Ping^2
> +static const hf_feature_info has_feature_table[] =
You might use constexpr for these tables?
OK either way, thanks!
Jason
next prev parent reply other threads:[~2023-10-26 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 14:27 Alex Coplan
2023-10-11 13:31 ` Alex Coplan
2023-10-25 10:28 ` Alex Coplan
2023-10-26 21:06 ` Jason Merrill [this message]
2023-11-03 10:39 ` Alex Coplan
2023-11-03 16:19 ` Marek Polacek
2023-11-17 15:12 ` Alex Coplan
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=6237945a-9b6a-45a0-94d2-8f150e4e3797@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 \
/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).