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/67683] Missed vectorization: shifts of an induction variable Date: Mon, 18 Mar 2024 07:36:47 +0000 [thread overview] Message-ID: <bug-67683-4-Vjy9poKayz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67683-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67683 --- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- /app/example.cpp:5:20: note: vect_is_simple_use: operand # RANGE [irange] short unsigned int [0, 2047][3294, 3294][6589, 6589][13179, 13179][26359, 26359][52719, 52719] val_16 = PHI <val_11(6), 52719(5)>, type of def: induction We detect it now. But then it is still not vectorized ...
next prev parent reply other threads:[~2024-03-18 7:36 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-09-22 17:21 [Bug tree-optimization/67683] New: " alalaw01 at gcc dot gnu.org 2015-09-23 8:16 ` [Bug tree-optimization/67683] " rguenth at gcc dot gnu.org 2015-10-06 15:15 ` alalaw01 at gcc dot gnu.org 2015-10-07 8:05 ` rguenth at gcc dot gnu.org 2024-03-18 7:29 ` pinskia at gcc dot gnu.org 2024-03-18 7:36 ` pinskia at gcc dot gnu.org [this message] 2024-03-18 9:16 ` liuhongt 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-67683-4-Vjy9poKayz@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).