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/89922] Loop on fixed size array is not unrolled and poorly optimized at -O2
Date: Wed, 22 Dec 2021 09:35:25 +0000	[thread overview]
Message-ID: <bug-89922-4-EJDl7VAb3B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-89922-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|middle-end                  |tree-optimization
           Severity|normal                      |enhancement

--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Estimating sizes for loop 1
 BB: 3, after_exit: 0
  size:   1 _1 = <retval>.data[j_16];
  size:   1 _2 = _1 + j_16;
  size:   1 <retval>.data[j_16] = _2;
  size:   1 j_13 = j_16 + 1;
   Induction variable computation will be folded away.
  size:   1 ivtmp_4 = ivtmp_18 - 1;
   Induction variable computation will be folded away.
  size:   2 if (ivtmp_4 != 0)
   Exit condition will be eliminated in peeled copies.
   Exit condition will be eliminated in last copy.
   Constant conditional.
 BB: 5, after_exit: 1
size: 7-4, last_iteration: 7-4
  Loop size: 7
  Estimated size after unrolling: 10
Not unrolling loop 1: size would grow.

       reply	other threads:[~2021-12-22  9:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-89922-4@http.gcc.gnu.org/bugzilla/>
2021-12-22  9:35 ` pinskia at gcc dot gnu.org [this message]
2021-12-27  4:11 ` 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-89922-4-EJDl7VAb3B@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).