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 87C7F3858D1E; Tue, 20 Dec 2022 09:29:31 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 87C7F3858D1E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1671528571;
	bh=exNGFkUziu70Yhu8yqb4OzDbb96gaEhliOtaKFMHyms=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=UrGERm60Z3S9T8CGb5YXBlb+ZME/AGg1KNeSgoh79bZGKF51MFU9jpwxnyYnMTLE0
	 E30Znjw4EkIr0K32GN8dKCQpDVrjqRVh8EUh7+ozE5JNi3I3+9tmCqPSGIBx/JOLHo
	 tFZPHb0FBHvq3yiNDFdnOpKyCv+XbYmzrx5XTeOY=
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107209] [13 Regression] ICE: verify_gimple failed
 (error: statement marked for throw, but doesn't)
Date: Tue, 20 Dec 2022 09:29:31 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: ice-on-invalid-code, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 13.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-107209-4-ciPgsgfJnr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107209-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107209-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=3D107209

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to ktkachov from comment #5)
> aarch64_could_trap_p returns true for it as it can raise an FP exception.
> Should that affect the nothrow attribute though? Shouldn't that be for C++
> exceptions only?

nothrow isn't just C++ attribute, it is also for C, which uses EH e.g. for
pthread_cancel or the non-call exceptions if -fexceptions.  Here
-fnon-call-exceptions is on and the builtin can trap, so it is right that t=
he
builtin isn't marked nothrow,
but then you need to either punt on folding that on GIMPLE if
flag_non_call_exceptions
and there is an EH edge for it, or ensure somehow the EH stuff is preserved
during the folding.=