public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/105746] vector<union>::resize causes Warray-bounds when optimizer uses __builtin_memcpy or __builtin_memmove since r12-2793-g81d6cdd335ffc60c Date: Tue, 29 Nov 2022 18:24:25 +0000 [thread overview] Message-ID: <bug-105746-4-q14KAoSxb0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105746-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105746 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to work| |13.0 Keywords| |needs-bisection Known to fail|13.0 | --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- Fixed by r13-4393-gcca06f0d6d76b0 on trunk? Reconfirmed with GCC 12, 11 and 10 but doesn't seem to happen with GCC 9.
next prev parent reply other threads:[~2022-11-29 18:24 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-27 0:08 [Bug c++/105746] New: vector<union>::resize causes Warray-bounds when optimizer uses __builtin_memcpy or __builtin_memmove albrecht.guendel at web dot de 2022-07-15 9:12 ` [Bug c++/105746] vector<union>::resize causes Warray-bounds when optimizer uses __builtin_memcpy or __builtin_memmove since r12-2793-g81d6cdd335ffc60c marxin at gcc dot gnu.org 2022-07-15 15:42 ` [Bug middle-end/105746] " msebor at gcc dot gnu.org 2022-11-29 18:24 ` rguenth at gcc dot gnu.org [this message] 2022-11-29 18:48 ` redi at gcc dot gnu.org 2022-12-27 14:28 ` marxin 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-105746-4-q14KAoSxb0@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).