From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 53BE5385842E; Sun, 16 Jul 2023 21:57:53 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 53BE5385842E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1689544673;
	bh=q/p52pzvkbIIM12xmNxfBLg+SkZVxopYL+gF3AX0k08=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=bm70oi2LNsUoR2BSQEu3rrGno1syPa8kw63DJV2TNo4LE+Ba/eIVdygJtidpuMoR8
	 THXdVBel4uZH7H1+3r3+Kf0Mg3aHvBy6G4GeWIzMwpKek0EIBRiQ++Ek+UNVzApbC5
	 v0CLVoZRRdc1Bm0tjcnndF9rvgymuVR9iRCpplI8=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/110649] [14 Regression] 25% sphinx3 spec2006 regression
 on Ice Lake and zen between g:acaa441a98bebc52 (2023-07-06 11:36) and
 g:55900189ab517906 (2023-07-07 00:23)
Date: Sun, 16 Jul 2023 21:57:52 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: missed-optimization, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-110649-4-YeeeEfINTu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110649-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110649-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

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

--- Comment #11 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:061f74c06735e1fa35b910ae0bcf01b61a74ec23

commit r14-2546-g061f74c06735e1fa35b910ae0bcf01b61a74ec23
Author: Jan Hubicka <jh@suse.cz>
Date:   Sun Jul 16 23:56:59 2023 +0200

    Fix profile update in scale_profile_for_vect_loop

    When vectorizing 4 times, we sometimes do
      for
        <4x vectorized body>
      for
        <2x vectorized body>
      for
        <1x vectorized body>

    Here the second two fors handling epilogue never iterates.
    Currently vecotrizer thinks that the middle for itrates twice.
    This turns out to be scale_profile_for_vect_loop that uses
    niter_for_unrolled_loop.

    At that time we know epilogue will iterate at most 2 times
    but niter_for_unrolled_loop does not know that the last iteration
    will be taken by the epilogue-of-epilogue and thus it think
    that the loop may iterate once and exit in middle of second
    iteration.

    We already do correct job updating niter bounds and this is
    just ordering issue.  This patch makes us to first update
    the bounds and then do updating of the loop.  I re-implemented
    the function more correctly and precisely.

    The loop reducing iteration factor for overly flat profiles is bit funn=
y,
but
    only other method I can think of is to compute sreal scale that would h=
ave
    similar overhead I think.

    Bootstrapped/regtested x86_64-linux, will commit it shortly.

    gcc/ChangeLog:

            PR middle-end/110649
            * tree-vect-loop.cc (scale_profile_for_vect_loop): Rewrite.
            (vect_transform_loop): Move scale_profile_for_vect_loop after
            upper bound updates.=