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/113678] SLP misses up vec_concat Date: Tue, 06 Feb 2024 17:14:06 +0000 [thread overview] Message-ID: <bug-113678-4-bpRlhyl1G2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113678-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113678 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Noticed the same with: ``` void f(unsigned char *a, unsigned char *b, unsigned char *c) { unsigned char t[8]; t[0] = a[0]; t[1] = a[1]; t[2] = a[2]; t[3] = a[3]; t[4] = b[0]; t[5] = b[1]; t[6] = b[2]; t[7] = b[3]; c[0] = t[0]; c[1] = t[1]; c[2] = t[2]; c[3] = t[3]; c[4] = t[4]; c[5] = t[5]; c[6] = t[6]; c[7] = t[7]; } ``` Adding `-fno-tree-vectorize` gives the best code even.
next prev parent reply other threads:[~2024-02-06 17:14 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-31 2:33 [Bug tree-optimization/113678] New: " pinskia at gcc dot gnu.org 2024-01-31 8:32 ` [Bug tree-optimization/113678] " rguenth at gcc dot gnu.org 2024-02-06 17:14 ` pinskia at gcc dot gnu.org [this message] 2024-02-06 17:46 ` pinskia 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-113678-4-bpRlhyl1G2@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).