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++/107861] C++ static_assert() does not honor -fwrapv, leading to compilation error
Date: Thu, 24 Nov 2022 20:56:14 +0000	[thread overview]
Message-ID: <bug-107861-4-ai42cKUy3H@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107861-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Markus F.X.J. Oberhumer from comment #6)
> Please note that I'm explicitly using "int_max" and not "INT_MAX",

It's a constexpr variable with the same value, so that makes no difference
whatsoever.

> and I'd
> appreciate if you could give me a link where the standard says this is
> "ill-formed". Thanks!

The condition is a static assert must be a constant-expression (C++20 9.1
[dcl.pre] paragraph 6).

int_max+1 is not a core constant (C++20 7.7 [expr.const] paragraph 5, bullet
5.7), so is not usable as the condition in a static_assert, so the program is
ill-formed.

  parent reply	other threads:[~2022-11-24 20:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 17:25 [Bug c++/107861] New: " markus at oberhumer dot com
2022-11-24 17:57 ` [Bug c++/107861] " pinskia at gcc dot gnu.org
2022-11-24 17:57 ` pinskia at gcc dot gnu.org
2022-11-24 18:18 ` markus at oberhumer dot com
2022-11-24 19:29 ` redi at gcc dot gnu.org
2022-11-24 19:34 ` redi at gcc dot gnu.org
2022-11-24 19:43 ` markus at oberhumer dot com
2022-11-24 20:56 ` redi at gcc dot gnu.org [this message]
2022-11-24 21:49 ` 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-107861-4-ai42cKUy3H@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).