public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fche at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113239] [13/14 regression] After 822a11a1e64, bogus -Warray-bounds warnings in std::vector Date: Mon, 22 Jan 2024 16:05:50 +0000 [thread overview] Message-ID: <bug-113239-4-FydAtRxi5i@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113239-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113239 --- Comment #7 from Frank Ch. Eigler <fche at redhat dot com> --- Wonder if this similar but different diagnostic is closely related: https://kojipkgs.fedoraproject.org//work/tasks/6259/112176259/build.log [...] inlined from ‘mutatee::instrument_dynprobe_target(BPatch_object*, dynprobe_target const&)’ at mutatee.cxx:444:22: /usr/include/c++/14/bits/stl_algobase.h:438:30: error: ‘memmove’ writing between 9 and 9223372036854775800 bytes into a region of size 0 overflows the destination [-Werror=stringop-overflow=] 438 | __builtin_memmove(__result, __first, sizeof(_Tp) * _Num); | ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In file included from /usr/include/c++/14/x86_64-redhat-linux/bits/c++allocator.h:33, from /usr/include/c++/14/bits/allocator.h:46, from /usr/include/c++/14/string:43: In member function ‘std::__new_allocator<BPatch_snippet*>::allocate(unsigned long, void const*)’, [...] where the c++ code in question is a straight vector<> foo; vector<> bar; foo.insert(foo.end(), bar.begin(), bar.end());
next prev parent reply other threads:[~2024-01-22 16:05 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-04 20:45 [Bug c++/113239] New: [13 " dimitry@unified-streaming.com 2024-01-04 21:10 ` [Bug tree-optimization/113239] " pinskia at gcc dot gnu.org 2024-01-06 22:49 ` dimitry@unified-streaming.com 2024-01-06 22:53 ` dimitry@unified-streaming.com 2024-01-08 14:57 ` [Bug tree-optimization/113239] [13/14 " rguenth at gcc dot gnu.org 2024-01-21 1:44 ` pinskia at gcc dot gnu.org 2024-01-21 1:46 ` pinskia at gcc dot gnu.org 2024-01-22 16:05 ` fche at redhat dot com [this message] 2024-01-22 16:34 ` dimitry@unified-streaming.com 2024-03-07 20:52 ` law at gcc dot gnu.org 2024-05-21 9:18 ` [Bug tree-optimization/113239] [13/14/15 " jakub 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-113239-4-FydAtRxi5i@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).