public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Darrell.Wright at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99535] g++ rejects valid code in constexpr copy ctor and volatile submember
Date: Thu, 11 Mar 2021 01:00:07 +0000	[thread overview]
Message-ID: <bug-99535-4-b1ISh9rEOR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99535-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99535

--- Comment #1 from Darrell Wright <Darrell.Wright at gmail dot com> ---
I was wrong, http://eel.is/c++draft/expr.const#5.8

  reply	other threads:[~2021-03-11  1:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11  0:51 [Bug c++/99535] New: " Darrell.Wright at gmail dot com
2021-03-11  1:00 ` Darrell.Wright at gmail dot com [this message]
2021-03-11 13:24 ` [Bug c++/99535] " 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-99535-4-b1ISh9rEOR@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).