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/18940] Loop is not vectorized when it should be (VRP)
Date: Mon, 07 Aug 2023 07:55:43 +0000	[thread overview]
Message-ID: <bug-18940-4-nG7uKGJOgn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-18940-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=18940

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |13.0
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Fixed in GCC 13.
DOM3 now optimizes it:

Optimizing statement _17 = D1360_10 > 0;
LKUP STMT _17 = D1360_10 gt_expr 0
2>>> STMT _17 = D1360_10 gt_expr 0
LKUP STMT D1360_10 le_expr 1
Optimizing statement _16 = (unsigned int) D1360_10;
LKUP STMT _16 = nop_expr D1360_10
2>>> STMT _16 = nop_expr D1360_10
Optimizing statement niters.3_18 = _17 ? _16 : 1;
  Replaced '_17' with constant '1'
 Registering value_relation (_16 pe32 D1360_10) (bb3) at _16 = (unsigned int)
D1360_10;
Applying pattern match.pd:4437, gimple-match.cc:176249
gimple_simplified to niters.3_18 = _16;
  Folded to: niters.3_18 = _16;

      parent reply	other threads:[~2023-08-07  7:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-18940-4@http.gcc.gnu.org/bugzilla/>
2021-12-25 22:56 ` pinskia at gcc dot gnu.org
2021-12-25 22:59 ` pinskia at gcc dot gnu.org
2023-08-07  7:55 ` pinskia at gcc dot gnu.org [this message]

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-18940-4-nG7uKGJOgn@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: link
Be 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).