public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "boris at kolpackov dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105329] New: Bogus restrict warning when assigning 1-char string literal to std::string Date: Thu, 21 Apr 2022 07:41:57 +0000 [thread overview] Message-ID: <bug-105329-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105329 Bug ID: 105329 Summary: Bogus restrict warning when assigning 1-char string literal to std::string Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: boris at kolpackov dot net Target Milestone: --- When compiling my codebase (build2) with GCC 12 (12.0.1 20220421) the output is littered with new bogus (AFAICS) -Wrestrict warnings that seems to be triggered by any attempt to assign or append a 1-char string literal to std::string: $ cat <<EOF >bogus-restrict.cxx #include <string> void f (std::string& s) { s = "5"; } EOF $ g++ -Wall -Wextra -O3 -c -std=c++23 bogus-restrict.cxx In file included from /home/boris/work/build2/tests/modules/gcc2/gcc-install/include/c++/12.0.1/string:40, from bogus-restrict.cxx:1: In static member function ‘static constexpr std::char_traits<char>::char_type* std::char_traits<char>::copy(char_type*, const char_type*, std::size_t)’, inlined from ‘static constexpr void std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::_S_copy(_CharT*, const _CharT*, size_type) [with _CharT = char; _Traits = std::char_traits<char>; _Alloc = std::allocator<char>]’ at /home/boris/work/build2/tests/modules/gcc2/gcc-install/include/c++/12.0.1/bits/basic_string.h:423:21, inlined from ‘constexpr std::__cxx11::basic_string<_CharT, _Traits, _Allocator>& std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::_M_replace(size_type, size_type, const _CharT*, size_type) [with _CharT = char; _Traits = std::char_traits<char>; _Alloc = std::allocator<char>]’ at /home/boris/work/build2/tests/modules/gcc2/gcc-install/include/c++/12.0.1/bits/basic_string.tcc:532:22, inlined from ‘constexpr std::__cxx11::basic_string<_CharT, _Traits, _Alloc>& std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::assign(const _CharT*) [with _CharT = char; _Traits = std::char_traits<char>; _Alloc = std::allocator<char>]’ at /home/boris/work/build2/tests/modules/gcc2/gcc-install/include/c++/12.0.1/bits/basic_string.h:1647:19, inlined from ‘constexpr std::__cxx11::basic_string<_CharT, _Traits, _Alloc>& std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::operator=(const _CharT*) [with _CharT = char; _Traits = std::char_traits<char>; _Alloc = std::allocator<char>]’ at /home/boris/work/build2/tests/modules/gcc2/gcc-install/include/c++/12.0.1/bits/basic_string.h:815:28, inlined from ‘void f(std::string&)’ at bogus-restrict.cxx:5:7: /home/boris/work/build2/tests/modules/gcc2/gcc-install/include/c++/12.0.1/bits/char_traits.h:431:56: warning: ‘void* __builtin_memcpy(void*, const void*, long unsigned int)’ accessing 9223372036854775810 or more bytes at offsets -4611686018427387902 and [-4611686018427387903, 4611686018427387904] may overlap up to 9223372036854775813 bytes at offset -3 [-Wrestrict] 431 | return static_cast<char_type*>(__builtin_memcpy(__s1, __s2, __n)); |
next reply other threads:[~2022-04-21 7:41 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-21 7:41 boris at kolpackov dot net [this message] 2022-04-21 11:15 ` [Bug tree-optimization/105329] " rguenth at gcc dot gnu.org 2022-04-21 20:50 ` amacleod at redhat dot com 2022-04-21 22:51 ` amacleod at redhat dot com 2022-04-22 10:31 ` aldyh at gcc dot gnu.org 2022-04-25 17:50 ` amacleod at redhat dot com 2022-04-25 22:25 ` mattias.ellert at physics dot uu.se 2022-04-26 15:04 ` [Bug tree-optimization/105329] [12 Regression] Bogus restrict warning when assigning 1-char string literal to std::string since r12-3347-g8af8abfbbace49e6 marxin at gcc dot gnu.org 2022-05-02 12:44 ` [Bug tree-optimization/105329] [12/13 " rguenth at gcc dot gnu.org 2022-05-02 12:45 ` rguenth at gcc dot gnu.org 2022-05-02 12:46 ` rguenth at gcc dot gnu.org 2022-05-02 12:57 ` rguenth at gcc dot gnu.org 2022-05-02 13:22 ` rguenth at gcc dot gnu.org 2022-05-02 13:33 ` jakub at gcc dot gnu.org 2022-05-02 13:58 ` jakub at gcc dot gnu.org 2022-05-02 16:04 ` jakub at gcc dot gnu.org 2022-05-02 19:43 ` jakub at gcc dot gnu.org 2022-05-02 22:08 ` redi at gcc dot gnu.org 2022-05-06 3:59 ` mattias.ellert at physics dot uu.se 2022-05-06 8:33 ` jakub at gcc dot gnu.org 2022-05-20 8:13 ` rguenth at gcc dot gnu.org 2022-07-26 12:05 ` jakub at gcc dot gnu.org 2022-09-12 9:37 ` cvs-commit at gcc dot gnu.org 2022-09-29 15:19 ` msebor at gcc dot gnu.org 2022-09-30 16:55 ` dan at stahlke dot org 2022-09-30 17:16 ` dan at stahlke dot org 2023-02-21 18:30 ` 49tbwddbqeazdawz at chyen dot cc 2023-02-21 19:28 ` redi at gcc dot gnu.org 2023-02-22 17:28 ` 49tbwddbqeazdawz at chyen dot cc 2023-02-22 17:52 ` redi at gcc dot gnu.org 2023-02-24 14:10 ` wielkiegie at gmail dot com 2023-05-08 12:24 ` [Bug tree-optimization/105329] [12/13/14 " rguenth 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-105329-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).