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 1DA153858D38; Tue, 20 Sep 2022 10:43:43 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1DA153858D38
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1663670623;
	bh=/QQ7Lk03L+BSj2hlVN5Zk8Nikq6RvurV1CbMfZqTqnw=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=F/5yneraA78AYGJR9zLnsmFEaBgvtrfQ4t8hHFAnS7cXzLOcNnMAsECZPiW2M9iFo
	 naWNPm9i3sGTeLbYTf9upwpPdBjY1OzMr1TJYeJHp5hnJ3Pa55qnO+3+v1bo3HMT8I
	 QlWrwhIBphKXiuG9MqBK5KUBhVw3PiZNM1Xhh2RY=
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106973] coroutine generator and setjmp
Date: Tue, 20 Sep 2022 10:43:42 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 12.2.0
X-Bugzilla-Keywords: C++-Coroutine
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-106973-4-WSrLShKRT5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106973-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106973-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=3D106973

--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The standard says:

> A call to setjmp or longjmp has undefined behavior if invoked in a suspen=
sion context of a coroutine (7.6.2.4).

Given that, I don't see why using setjmp in example would be useful.=