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 3DB5B3AA8013; Tue, 30 Aug 2022 13:38:56 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3DB5B3AA8013
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1661866736;
	bh=5bkERykNf+8AHrry0x6oJBUcG99MkCzopsiV80QdHos=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=TUv1MoNB+uyBtUECpCzanVG5zK2OpgNNiJP2gtYcblNLD2w4xHS6sm/c3OQrYRI0U
	 7kDGZxUPSVxrDF+9z1rTLysRHHvVpdZDjUZw2kX/f1s7VZmLgYRsK0iuwUIJtZz+3t
	 sTRITIRnetaQ1VgInM1xlGD3JWy78v7n2ZM/MYJA=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/73550] Another wrong -Wmaybe-uninitialized
 warning in switch statement
Date: Tue, 30 Aug 2022 13:38:56 +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: 7.0
X-Bugzilla-Keywords: diagnostic, missed-optimization
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: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-73550-4-EluYUby4Fb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-73550-4@http.gcc.gnu.org/bugzilla/>
References: <bug-73550-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=3D73550

--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:

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

commit r13-2279-gce776225249d99b089d02424b9472811a6bbd7f5
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Aug 30 14:37:23 2022 +0200

    tree-optimization/73550 - apply MAX_NUM_CHAINS consistently

    The MAX_NUM_CHAINS is applied once with <=3D and once with < which
    results in the chains not limited but analyis dropped completely.
    That's one issue in the PR.

            PR tree-optimization/73550
            * gimple-predicate-analysis.cc (predicate::init_from_control_de=
ps):
            Do not apply MAX_NUM_CHAINS again.=