From: Iain Sandoe <iain@sandoe.co.uk>
To: Alex Coplan <alex.coplan@arm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Jason Merrill <jason@redhat.com>, Nathan Sidwell <nathan@acm.org>
Subject: Re: [PATCH v2] c++: Accept elaborated-enum-base in system headers
Date: Thu, 15 Jun 2023 10:50:09 +0100 [thread overview]
Message-ID: <C68BA2B8-4B0E-45A8-85C0-599FDF007BA4@sandoe.co.uk> (raw)
In-Reply-To: <ZInBSpWMc7qz9m53@arm.com>
Hi Alex
> On 14 Jun 2023, at 14:31, Alex Coplan <alex.coplan@arm.com> wrote:
>
> Hi,
>
> This is a v2 patch addressing feedback for:
> https://gcc.gnu.org/pipermail/gcc-patches/2023-June/621050.html
>
> macOS SDK headers using the CF_ENUM macro can expand to invalid C++ code
> of the form:
>
> typedef enum T : BaseType T;
>
> i.e. an elaborated-type-specifier with an additional enum-base.
> Upstream LLVM can be made to accept the above construct with
> -Wno-error=elaborated-enum-base.
>
> This patch adds the -Welaborated-enum-base warning to GCC and adjusts
> the C++ parser to emit this warning instead of rejecting this code
> outright.
>
> The macro expansion in the macOS headers occurs in the case that the
> compiler declares support for enums with underlying type using
> __has_feature, see
> https://gcc.gnu.org/pipermail/gcc-patches/2023-May/618450.html
>
> GCC rejecting this construct outright means that GCC fails to bootstrap
> on Darwin in the case that it (correctly) implements __has_feature and
> declares support for C++ enums with underlying type.
>
> With this patch, GCC can bootstrap on Darwin in combination with the
> (WIP) __has_feature patch posted at:
> https://gcc.gnu.org/pipermail/gcc-patches/2023-May/617878.html
>
> Bootstrapped/regtested on aarch64-linux-gnu and x86_64-apple-darwin.
> OK for trunk?
For the record, I have tried this on Darwin21 and Darwin17 together with
my patches for __attribute__((availability(….))) which is also instrumental
in exposing more of the SDK content than we have previously been able
to parse on GCC. Bootstrap succeeded there, and I will try on some older
versions as time permits (likely after WG21 meeting is done).
thanks
Iain
>
> Thanks,
> Alex
>
> gcc/c-family/ChangeLog:
>
> * c.opt (Welaborated-enum-base): New.
>
> gcc/cp/ChangeLog:
>
> * parser.cc (cp_parser_enum_specifier): Don't reject
> elaborated-type-specifier with enum-base, instead emit new
> Welaborated-enum-base warning.
>
> gcc/testsuite/ChangeLog:
>
> * g++.dg/cpp0x/enum40.C: Adjust expected diagnostics.
> * g++.dg/cpp0x/forw_enum6.C: Likewise.
> * g++.dg/cpp0x/elab-enum-base.C: New test.
> <patch.txt>
next prev parent reply other threads:[~2023-06-15 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 13:31 Alex Coplan
2023-06-15 9:50 ` Iain Sandoe [this message]
2023-06-15 11:47 ` 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=C68BA2B8-4B0E-45A8-85C0-599FDF007BA4@sandoe.co.uk \
--to=iain@sandoe.co.uk \
--cc=alex.coplan@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.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).