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++/70248] constexpr initialization with unspecified equality expression accepted
Date: Thu, 15 Oct 2020 11:19:41 +0000	[thread overview]
Message-ID: <bug-70248-4-XVVVuHUiSC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-70248-4@http.gcc.gnu.org/bugzilla/>

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2020-10-15
           Severity|minor                       |normal
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW

--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Another example with a relational operator:

constexpr const char* s = "";
constexpr const char* n = nullptr;
constexpr bool b = s > n;

The result of the comparison is unspecified because the pointers are not equal
and don't point to subobjects of the same object.

Clang, EDG and MSVC all reject it as expected.

       reply	other threads:[~2020-10-15 11:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-70248-4@http.gcc.gnu.org/bugzilla/>
2020-10-15 11:19 ` redi at gcc dot gnu.org [this message]
2020-10-15 11:24 ` redi at gcc dot gnu.org
2020-10-15 15:03 ` mpolacek at gcc dot gnu.org
2023-08-22 18:35 ` pkeir at outlook dot com
2024-01-03 13:00 ` redi at gcc dot gnu.org
2024-01-03 13:01 ` redi at gcc dot gnu.org
2024-01-03 13:07 ` 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-70248-4-XVVVuHUiSC@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).