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 tree-optimization/98908] Failure to optimize arithmetic involving struct members into operating on the entire struct Date: Tue, 02 Feb 2021 07:58:32 +0000 [thread overview] Message-ID: <bug-98908-4-YfiR9sc5EZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98908-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98908 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |53947 Status|UNCONFIRMED |NEW Last reconfirmed| |2021-02-02 Ever confirmed|0 |1 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- The vectorizer would do this if there's a V2QImode or generic vect would be enabled for sth not just word_mode size. For SLP vectorization it should be easy to restrict the search space (aka choose a prefered SIMD mode). Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947 [Bug 53947] [meta-bug] vectorizer missed-optimizations
next prev parent reply other threads:[~2021-02-02 7:58 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-01 8:10 [Bug tree-optimization/98908] New: " gabravier at gmail dot com 2021-02-02 7:58 ` rguenth at gcc dot gnu.org [this message] 2021-09-03 0:15 ` [Bug tree-optimization/98908] " gabravier at gmail dot com 2021-09-03 0:27 ` pinskia at gcc dot gnu.org 2021-09-03 0:28 ` pinskia at gcc dot gnu.org 2021-09-03 0:31 ` gabravier at gmail dot com 2021-09-03 0:41 ` gabravier at gmail dot com 2021-09-03 0:59 ` pinskia at gcc dot gnu.org 2021-09-03 1:09 ` gabravier at gmail dot com 2021-09-03 1:11 ` gabravier at gmail dot com 2021-09-03 1:31 ` [Bug tree-optimization/98908] [11 Regression] arithmetic involving struct members into operating on the entire struct fails at -O3 pinskia at gcc dot gnu.org 2021-09-03 1:38 ` pinskia at gcc dot gnu.org 2022-04-21 7:48 ` rguenth at gcc dot gnu.org 2023-05-29 10:04 ` 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-98908-4-YfiR9sc5EZ@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).