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 tree-optimization/106199] incorrect memcpy writing 1 or more bytes into a region of size 0 overflows the destination with std::vector::insert . Date: Tue, 05 Jul 2022 23:17:34 +0000 [thread overview] Message-ID: <bug-106199-4-9kqpmPmj9A@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106199-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106199 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|middle-end |tree-optimization Summary|vector::insert optimization |incorrect memcpy writing 1 |is broken with gcc-12 |or more bytes into a region | |of size 0 overflows the | |destination with | |std::vector::insert . --- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> --- /opt/compiler-explorer/gcc-trunk-20220705/include/c++/13.0.0/bits/stl_algobase.h:431:30: error: 'void* __builtin_memcpy(void*, const void*, long unsigned int)' writing 1 or more bytes into a region of size 0 overflows the destination [-Werror=stringop-overflow=]
next prev parent reply other threads:[~2022-07-05 23:17 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-05 10:02 [Bug c++/106199] New: vector::insert optimization is broken with gcc-12 hewillk at gmail dot com 2022-07-05 10:07 ` [Bug c++/106199] " hewillk at gmail dot com 2022-07-05 10:18 ` hewillk at gmail dot com 2022-07-05 16:30 ` [Bug middle-end/106199] " redi at gcc dot gnu.org 2022-07-05 23:17 ` pinskia at gcc dot gnu.org [this message] 2022-07-05 23:17 ` [Bug tree-optimization/106199] [12 Regression] incorrect warning: memcpy writing 1 or more bytes into a region of size 0 overflows the destination with std::vector::insert pinskia at gcc dot gnu.org 2022-07-25 15:15 ` [Bug tree-optimization/106199] [12/13 " rguenth at gcc dot gnu.org 2022-11-29 15:58 ` redi at gcc dot gnu.org 2022-11-29 17:14 ` cvs-commit at gcc dot gnu.org 2023-04-20 13:57 ` cvs-commit 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-106199-4-9kqpmPmj9A@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).