public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/111073] [13/14 regression] False-positive -Wstringop-overflow when building gdb from trunk Date: Sat, 19 Aug 2023 06:49:25 +0000 [thread overview] Message-ID: <bug-111073-4-dGPJ0QVaWI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111073-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111073 Sam James <sjames at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |88443 --- Comment #1 from Sam James <sjames at gcc dot gnu.org> --- I can reproduce it with: ``` $ g++-14 -c infcall.ii -O2 -Werror=stringop-overflow [...] /usr/lib/gcc/x86_64-pc-linux-gnu/14/include/g++-v14/bits/stl_algobase.h:437:30: error: ‘void* __builtin_memmove(void*, const void*, long unsigned int)’ writing 9 or more bytes into a region of size 0 overflows the destination [-Werror=stringop-overflow=] 437 | __builtin_memmove(__result, __first, sizeof(_Tp) * _Num); | ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [...] ``` Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88443 [Bug 88443] [meta-bug] bogus/missing -Wstringop-overflow warnings
next prev parent reply other threads:[~2023-08-19 6:49 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-19 6:48 [Bug c++/111073] New: " sjames at gcc dot gnu.org 2023-08-19 6:49 ` sjames at gcc dot gnu.org [this message] 2023-08-19 6:51 ` [Bug c++/111073] [13/14 regression] False-positive -Wstringop-overflow when building gdb from trunk with -D_GLIBCXX_ASSERTIONS sjames at gcc dot gnu.org 2023-08-21 8:14 ` [Bug tree-optimization/111073] " rguenth at gcc dot gnu.org 2024-03-07 23:24 ` law at gcc dot gnu.org 2024-05-21 9:16 ` [Bug tree-optimization/111073] [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-111073-4-dGPJ0QVaWI@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).