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 middle-end/111696] [11/12/13/14 Regression] Spurious -Wstringop-overflow Date: Wed, 04 Oct 2023 22:50:21 +0000 [thread overview] Message-ID: <bug-111696-4-rDSvn2z4rA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111696-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111696 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- The vectorizer has not much to do with the warning issue except for the IR change into FRE. Before fre5: _11 = &last_14(D)->s; memcpy (_11, &cur.s, 24); After: vectp.7_19 = &accum_13(D)->sD.4831.aD.4827[0]; ... vectp.10_9 = &last_14(D)->sD.4831.aD.4827[0]; ... # .MEM_26 = VDEF <.MEM_12(D)> MEM <vector(2) long unsigned intD.17> [(long unsigned intD.17 *)vectp.7_19] = vect__5.13_24; # .MEM_17 = VDEF <.MEM_26> MEM <unsigned charD.31[24]> [(charD.11 * {ref-all})vectp.10_9] = MEM <unsigned charD.31[24]> [(charD.11 * {ref-all})&curD.4832];
next prev parent reply other threads:[~2023-10-04 22:50 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-04 18:03 [Bug middle-end/111696] New: " stilor at att dot net 2023-10-04 22:50 ` pinskia at gcc dot gnu.org [this message] 2023-10-04 22:55 ` [Bug middle-end/111696] " pinskia at gcc dot gnu.org 2023-10-05 7:38 ` rguenth at gcc dot gnu.org 2024-03-07 21:06 ` law 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-111696-4-rDSvn2z4rA@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).