From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5B52F3858D35; Mon, 15 Jun 2020 19:11:40 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5B52F3858D35 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1592248300; bh=2EpQ3MoMulSf0wlOczzh8wccgVQ1QlCJOkHpxiiSGLg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Bs7DibNGfvpHOyWITNiFSApZ8bQ1mcXDMDE+rUfvyeR0nmB8jT3egP5mvo0xR47Ki zK3K9hp9T/tJCPAIzdpQ4/AbVqJaYSEgx10gprHFpOp38RY9lWNX2qlZcnP/Zj9Evy iY7eIs1ry0LIZgbVFVkHPLpMK/TUmX02GN+crhcQ= From: "law at redhat dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/95649] [11 Regression] ICE during GIMPLE pass: cunroll since r11-1146-g1396fa5b91cfa0b3 Date: Mon, 15 Jun 2020 19:11:40 +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: 11.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: law at redhat dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: aldyh at gcc dot gnu.org X-Bugzilla-Target-Milestone: 11.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jun 2020 19:11:40 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95649 Jeffrey A. Law changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |law at redhat dot com --- Comment #6 from Jeffrey A. Law --- What precisely is causing the problem? Are we doing something like mucking= up the loop closed ssa form? Or do these passes have internal data that's invalidated by the PHI changes? Or something else? Hard to know what to recommend here without more info.=