From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E07963851C39; Thu, 14 May 2020 18:39:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E07963851C39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1589481564; bh=96NODJ97g7oFupWjJ9eRFwaHBkqdhzVzLHluo0wOLrE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=YI7VpRHWXdRBeyKEMlNPdRTw00Wc5z55NgOXThJ+fvikqOlcEEDHrqGS5FcBZe3Mo 60uHP8fE/Z1iNpXhSO+jVgM3VpXetCE1srPlMfNvoZo7Y6dtCvL/bpUPI/8T6Xa/pc k9I3KT+/ExdR/5ZNRZOgogYA93QT2RTKF23GtXs8= From: "tkoenig at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/95053] [11 regression] ICE in f951: gfc_divide() Date: Thu, 14 May 2020 18:39:24 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 11.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tkoenig at gcc dot gnu.org X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: anlauf at gcc dot gnu.org X-Bugzilla-Target-Milestone: 11.0 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 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: Thu, 14 May 2020 18:39:25 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95053 --- Comment #26 from Thomas Koenig --- (In reply to wschmidt from comment #24) > I'm afraid I disagree.=C2=A0 A divide-by-zero that cannot ever be execute= d is=20 > not an error. Well, there is PR90302. We could insert some piece of code into the IL. A warning or an error could then be issued if the piece of code is still present after the final optimization. It would make a nice project, and remove a few more false positives as well.=