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 B8F6C383FB93; Fri, 10 Feb 2023 17:44:24 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B8F6C383FB93
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1676051064;
	bh=0dx3DuSHv2infpdo+5We3RUNJrTtReqycCLhsEk4DL0=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=r6XMQ78iLbiJ4N0RsEGfmdce73i/bxelDFmxl0RuI00X/GdUDGDURAd30H8V/EjVH
	 COD1exVlO4zzih0Yv73wcKIyHTt3EMSa7eNuCSaTdRIe+J/qUMT2ucnG2Fal6UGCzi
	 0pZac5GLMYngONO5ykvBM5x+S+97MjqLto/gLgU8=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107997] [10/11/12/13 Regression]
 r13-4389-gfd8dd6c0384969 probably uncovered an issue building the Linux
 kernel
Date: Fri, 10 Feb 2023 17:44:21 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.5
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-107997-4-3qQ9Q4VIEn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107997-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107997-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=3D107997

--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:89daf0dd6f1748077c03fbeb27ca5980a0b9abd5

commit r12-9125-g89daf0dd6f1748077c03fbeb27ca5980a0b9abd5
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Sat Dec 10 16:50:39 2022 +0100

    ivopts: Fix IP_END handling for asm goto [PR107997]

    The following testcase ICEs, because the latch bb ends with
    asm goto which has both fallthrough to the header and one or more labels
    in the header too.  In that case there is just a single edge out of the
    latch block, but still the asm goto is stmt_ends_bb_p statement, yet
    ivopts decides to emit an IV bump at the IP_END position and inserts
    it into the same bb as the asm goto after it, which then fails verifica=
tion
    (control flow in the middle of bb).

    The following patch fixes it by splitting the latch -> header edge in t=
hat
    case and inserting into the newly created bb, where split_edge ->
    redirect_edge_and_branch is able to deal with this case correctly.

    2022-12-10  Jakub Jelinek  <jakub@redhat.com>

            PR tree-optimization/107997
            * tree-ssa-loop-ivopts.cc: Include cfganal.h.
            (create_new_iv) <case IP_END>: If ip_end_pos bb is non-empty and
ends
            with a stmt which ends bb, instead of adding iv update after it
split
            the latch edge and insert iterator into the new latch bb.

            * gcc.c-torture/compile/pr107997.c: New test.

    (cherry picked from commit 7676235f690e624b7ed41a22b22ce8ccfac1492f)=