public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "de34 at live dot cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/110619] Dangling pointer returned from constexpr function converts in nullptr
Date: Wed, 12 Jul 2023 01:51:20 +0000 [thread overview]
Message-ID: <bug-110619-4-o6VjEo83Ht@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110619-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110619
Jiang An <de34 at live dot cn> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |de34 at live dot cn
--- Comment #4 from Jiang An <de34 at live dot cn> ---
(In reply to Andrew Pinski from comment #1)
> I would have expected this to be undefined ...
> So the static_assert could work or not.
If this were undefined (not true IIUC), static_assert would be required not to
work because the condition expression is not a constant expression
([expr.const]/5.8).
We should keep in mind that all kinds of core UB that may occur within
(tentative) constant evaluation (except for violation of [[assume]], currently)
are not totally undefined, since they must cause constant evaluation failure.
CWG issue should be submitted if such detection is unimplementable.
next prev parent reply other threads:[~2023-07-12 1:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 18:39 [Bug c++/110619] New: " fchelnokov at gmail dot com
2023-07-10 18:43 ` [Bug c++/110619] " pinskia at gcc dot gnu.org
2023-07-10 18:44 ` pinskia at gcc dot gnu.org
2023-07-10 19:04 ` fchelnokov at gmail dot com
2023-07-12 1:51 ` de34 at live dot cn [this message]
2023-07-13 19:02 ` ppalka at gcc dot gnu.org
2023-07-26 1:45 ` cvs-commit at gcc dot gnu.org
2023-08-07 5:04 ` peter at cordes dot ca
2023-08-07 7:41 ` fchelnokov at gmail dot com
2023-08-07 9:12 ` 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-110619-4-o6VjEo83Ht@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).