From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id CDB5C396E054; Thu, 14 May 2020 14:57:37 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CDB5C396E054 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1589468257; bh=pVnVuGxvOgj1tMmCbY142uC91Q67XMTTI5QkPU4AHiA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=GahYlFzwPpfZOZAQjocEV96rKb442Z0J1aW75IyWSgXKUOfgRmR2EZCCVn+9SMaDf IOlLb7yZQAZrQzOKSJNl0jY4Jq2TDNJVZKMaUjx3EOSuIzRDbuGl25bntMSmKBhZGo BOcdOYX7hjKFHvYHdHYBJL9bClslmf0Py40Q0B6E= From: "wschmidt 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 14:57:37 +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: wschmidt 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: 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: Thu, 14 May 2020 14:57:37 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95053 Bill Schmidt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wschmidt at gcc dot gnu.org --- Comment #22 from Bill Schmidt --- Breaking legitimate code, even if "borderline," does not seem right to me.= =20=20 Zero division is generally a runtime exception because of such cases. You write code for a general case, then later you discover "oh, well, we co= uld make this variable zero for our specific usage," and now the compiler throw= s a fit? Seems like this is warning-level stuff.=