public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/77689] Missing vectorization lead to huge performance loss
Date: Fri, 28 Jul 2023 14:19:31 +0000	[thread overview]
Message-ID: <bug-77689-4-xLtEc1iYrp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-77689-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #18 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jan Hubicka <hubicka@gcc.gnu.org>:

https://gcc.gnu.org/g:f5fb9ff2396fd41fdd2e6d35a412e936d2d42f75

commit r14-2852-gf5fb9ff2396fd41fdd2e6d35a412e936d2d42f75
Author: Jan Hubicka <jh@suse.cz>
Date:   Fri Jul 28 16:18:32 2023 +0200

    loop-split improvements, part 3

    extend tree-ssa-loop-split to understand test of the form
     if (i==0)
    and
     if (i!=0)
    which triggers only during the first iteration.  Naturally we should
    also be able to trigger last iteration or split into 3 cases if
    the test indeed can fire in the middle of the loop.

    Last iteration is bit trickier pattern matching so I want to do it
    incrementally, but I implemented easy case using value range that handled
    loops with constant iterations.

    The testcase gets misupdated profile, I will also fix that incrementally.

    gcc/ChangeLog:

            PR middle-end/77689
            * tree-ssa-loop-split.cc: Include value-query.h.
            (split_at_bb_p): Analyze cases where EQ/NE can be turned
            into LT/LE/GT/GE; return updated guard code.
            (split_loop): Use guard code.

    gcc/testsuite/ChangeLog:

            PR middle-end/77689
            * g++.dg/tree-ssa/loop-split-1.C: New test.

      parent reply	other threads:[~2023-07-28 14:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-77689-4@http.gcc.gnu.org/bugzilla/>
2021-08-25  6:07 ` pinskia at gcc dot gnu.org
2021-08-25  7:38 ` crazylht at gmail dot com
2023-07-28  8:12 ` hubicka at gcc dot gnu.org
2023-07-28 11:53 ` hubicka at gcc dot gnu.org
2023-07-28 13:11 ` hubicka at gcc dot gnu.org
2023-07-28 14:19 ` cvs-commit 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-77689-4-xLtEc1iYrp@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).