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/104368] [12 Regression] Failure to vectorise conditional grouped accesses after PR102659 Date: Thu, 03 Feb 2022 23:42:23 +0000 [thread overview] Message-ID: <bug-104368-4-Q1DvUZqpHX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104368-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104368 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |12.0 Blocks| |53947 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:[~2022-02-03 23:42 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-03 14:51 [Bug tree-optimization/104368] New: " rsandifo at gcc dot gnu.org 2022-02-03 23:42 ` pinskia at gcc dot gnu.org [this message] 2022-02-04 7:58 ` [Bug tree-optimization/104368] " rguenth at gcc dot gnu.org 2022-05-06 8:32 ` [Bug tree-optimization/104368] [12/13 " jakub at gcc dot gnu.org 2022-07-26 13:01 ` rguenth at gcc dot gnu.org 2023-05-08 12:23 ` [Bug tree-optimization/104368] [12/13/14 " rguenth 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-104368-4-Q1DvUZqpHX@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).