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 target/110727] [14 Regression] gcc.target/aarch64/sve/aarch64-sve.exp has two new failures since commit 061f74c0673
Date: Fri, 21 Jul 2023 17:38:49 +0000	[thread overview]
Message-ID: <bug-110727-4-PgVP5KcnyD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110727-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 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:a31ef26b056d0c4f0a9f08b6eb81456ea257298e

commit r14-2716-ga31ef26b056d0c4f0a9f08b6eb81456ea257298e
Author: Jan Hubicka <jh@suse.cz>
Date:   Fri Jul 21 19:38:26 2023 +0200

    Avoid scaling flat loop profiles of vectorized loops

    As discussed, when vectorizing loop with static profile, it is not always
good idea
    to divide the header frequency by vectorization factor because the profile
may
    not realistically represent the expected number of iterations.  Since in
such cases
    we default to relatively low iteration counts (based on average for
spec2k17), this
    will make vectorized loop body look cold.

    This patch makes vectorizer to look for flat profiles and only possibly
reduce the
    profile by known upper bound on iteration counts.

    gcc/ChangeLog:

            PR target/110727
            * tree-vect-loop.cc (scale_profile_for_vect_loop): Avoid scaling
flat
            profiles by vectorization factor.
            (vect_transform_loop): Check for flat profiles.

  parent reply	other threads:[~2023-07-21 17:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 19:24 [Bug target/110727] New: " thiago.bauermann at linaro dot org
2023-07-19  6:49 ` [Bug target/110727] [14 Regression] " rguenth at gcc dot gnu.org
2023-07-21 17:38 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-21 22:46 ` thiago.bauermann at linaro dot org
2023-08-06 20:49 ` hubicka 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-110727-4-PgVP5KcnyD@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).