public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "peifeng2005 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/97432] Casting away constness in the drafts [conv.qual] a cv-decomposition exists in the following examples but fails in gcc
Date: Thu, 15 Oct 2020 08:06:46 +0000	[thread overview]
Message-ID: <bug-97432-4-K2I0tGCTMJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97432-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Ray Zhang <peifeng2005 at gmail dot com> ---
Hi, I actually spoke with Richard Smith about the same ticket (since clang was
also involved in the comparison here), and I found that if we were conforming
to the draft, the first case should also fail to compile. The discussion is
linked [here](https://bugs.llvm.org/show_bug.cgi?id=47848).

The issue now is that passing -pedantic-errors into GCC still allows for the
first case to pass. This shouldn't work since we find one such qual conv to
fail (const int vs. int).

      parent reply	other threads:[~2020-10-15  8:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-15  0:10 [Bug c++/97432] New: " peifeng2005 at gmail dot com
2020-10-15  0:12 ` [Bug c++/97432] " peifeng2005 at gmail dot com
2020-10-15  8:06 ` peifeng2005 at gmail dot com [this message]

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-97432-4-K2I0tGCTMJ@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).