public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pdimov at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/113200] New: std::char_traits<char>::move is not constexpr when the argument is a string literal Date: Tue, 02 Jan 2024 15:41:44 +0000 [thread overview] Message-ID: <bug-113200-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113200 Bug ID: 113200 Summary: std::char_traits<char>::move is not constexpr when the argument is a string literal Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: pdimov at gmail dot com Target Milestone: --- ``` #include <string> #include <cassert> template<std::size_t N> struct S { char data_[ N ]; using traits_type = std::char_traits<char>; constexpr S( char const* p ): data_{} { std::size_t n = traits_type::length( p ); assert( n < N ); traits_type::move( data_, p, n + 1 ); } }; template<std::size_t N> S( char const(&)[N] ) -> S<N>; constexpr S s( "test" ); ``` (https://godbolt.org/z/PofY8MP6G) fails with ``` In file included from /opt/compiler-explorer/gcc-trunk-20240102/include/c++/14.0.0/string:42, from <source>:1: <source>:22:23: in 'constexpr' expansion of 'S<5>(((const char*)"test"))' <source>:16:26: in 'constexpr' expansion of 'std::char_traits<char>::move(((char*)(&((S<5>*)this)->S<5>::data_)), p, (n + 1))' /opt/compiler-explorer/gcc-trunk-20240102/include/c++/14.0.0/bits/char_traits.h:423:50: in 'constexpr' expansion of '__gnu_cxx::char_traits<char>::move(__s1, __s2, __n)' /opt/compiler-explorer/gcc-trunk-20240102/include/c++/14.0.0/bits/char_traits.h:230:20: error: '(((const __gnu_cxx::char_traits<char>::char_type*)(& s.S<5>::data_)) == ((const char*)"test"))' is not a constant expression 230 | if (__s1 == __s2) // unlikely, but saves a lot of work | ~~~~~^~~~~~~ ``` (Reduced from a similar failure in Boost.StaticString.)
next reply other threads:[~2024-01-02 15:41 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-02 15:41 pdimov at gmail dot com [this message] 2024-01-02 16:45 ` [Bug c++/113200] " pinskia at gcc dot gnu.org 2024-01-02 16:47 ` [Bug libstdc++/113200] " pinskia at gcc dot gnu.org 2024-01-02 16:49 ` 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@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).