public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/113200] std::char_traits<char>::move is not constexpr when the argument is a string literal Date: Tue, 02 Jan 2024 16:47:43 +0000 [thread overview] Message-ID: <bug-113200-4-klgQApV8Yw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113200-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113200 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|c++ |libstdc++ --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- I take that back, clang provideds a better error message on why `&a == "string"` is not constexpr: ``` /opt/compiler-explorer/gcc-snapshot/lib/gcc/x86_64-linux-gnu/14.0.0/../../../../include/c++/14.0.0/bits/char_traits.h:230:13: note: comparison of addresses of literals has unspecified value 230 | if (__s1 == __s2) // unlikely, but saves a lot of work | ^ ```
next prev parent reply other threads:[~2024-01-02 16:47 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-02 15:41 [Bug libstdc++/113200] New: " pdimov at gmail dot com 2024-01-02 16:45 ` [Bug c++/113200] " pinskia at gcc dot gnu.org 2024-01-02 16:47 ` pinskia at gcc dot gnu.org [this message] 2024-01-02 16:49 ` [Bug libstdc++/113200] " pdimov at gmail dot com 2024-01-02 16:51 ` pdimov at gmail dot com 2024-01-03 11:13 ` [Bug c++/113200] " redi at gcc dot gnu.org 2024-01-03 11:23 ` [Bug libstdc++/113200] " redi at gcc dot gnu.org 2024-01-03 12:57 ` redi at gcc dot gnu.org 2024-01-03 13:01 ` redi at gcc dot gnu.org 2024-01-04 1:58 ` de34 at live dot cn 2024-01-05 10:23 ` cvs-commit at gcc dot gnu.org 2024-01-05 11:46 ` redi at gcc dot gnu.org 2024-01-06 13:40 ` cvs-commit at gcc dot gnu.org 2024-01-11 23:16 ` cvs-commit at gcc dot gnu.org 2024-01-11 23:17 ` 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-113200-4-klgQApV8Yw@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: linkBe 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).