From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8813638582A1; Tue, 7 Nov 2023 19:18:08 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8813638582A1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1699384688; bh=//qKOdLXkEWv2vElv4pal9bBAQYE50hqarnjTlDNBKU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=s5q9lLLVhcWisVjK2wYuphuSxcfHXk97x3frW/cR5DKNsFHR2oIcMBojIAd4Lgmiu OltGG7YjTIULLIhjgPPkifQOpw6OcBhnvdpPB7bzebJ8yLN9NLLLGFPh64hoY3AD0T WQta1JwTYuR4gc0caaKrpt9Pr7/OlSTrQfiLZp2c= From: "amacleod at redhat dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/106511] [13/14 Regression] New -Werror=maybe-uninitialized since r13-1268-g8c99e307b20c502e Date: Tue, 07 Nov 2023 19:18:07 +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: diagnostic, missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: amacleod at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.3 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D106511 --- Comment #8 from Andrew Macleod --- (In reply to Richard Biener from comment #2) > VRP could use max_stmt_executions here (note it doesn't properly handle l= oop > nests so the name is somewhat misleading) Do you have to ask for max_stmt_executions on each loop nest for the stmt to get the real total? and multiple them all together? or can you only count= on loop_outer()?=