public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106357] [12/13 Regression] direct-list-initialization of enum class from a variable of another enum class type fails
Date: Tue, 19 Jul 2022 16:55:27 +0000 [thread overview]
Message-ID: <bug-106357-4-tSUuCxwATk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106357-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106357
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> I think the testcase is invalid as the enum does not have "fixed underlying
> type"
Scoped enums always have a fixed underlying type.
next prev parent reply other threads:[~2022-07-19 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 16:00 [Bug c++/106357] New: " enolan at alumni dot cmu.edu
2022-07-19 16:07 ` [Bug c++/106357] " pinskia at gcc dot gnu.org
2022-07-19 16:10 ` pinskia at gcc dot gnu.org
2022-07-19 16:55 ` redi at gcc dot gnu.org [this message]
2022-07-19 16:58 ` redi at gcc dot gnu.org
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=bug-106357-4-tSUuCxwATk@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).