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 A2731384E3BD; Sat, 26 Nov 2022 16:28:21 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A2731384E3BD
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1669480101;
	bh=q3fxKFV/Swtq7AAn4K72B9i1ueA14TDum9LfTi/+qSk=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Nuw8cYILukFnvLRCFuUjrkv3sROuQoabqZz+YsJBBH2F9NA9R7rfX0ppFfEJNKNlQ
	 kSbEOsqXhrHKQKd/2L0cG8DEcA6K59nOHLOks5sKhSGn0lcIycf/uAaOX0Kuj15eW0
	 m5QqrOF/Fmk2gwFc8pLk/gwQT4/1zujawJG6hdBE=
From: "adrian.perl at web dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99576] [coroutines] destructor of a temporary called too
 early within co_await expression
Date: Sat, 26 Nov 2022 16:28:19 +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: 10.2.1
X-Bugzilla-Keywords: C++-coroutines, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: adrian.perl at web dot de
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-99576-4-IUxCrkKau8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-99576-4@http.gcc.gnu.org/bugzilla/>
References: <bug-99576-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=3D99576

--- Comment #7 from Adrian Perl <adrian.perl at web dot de> ---
Bootstrapping was successfull and the tests are currently running. Some of =
the
tests have failed, but they don't seem to be related to coroutines. Should I
test twice, with and without the patch, in order to see the actual impact?=
=20

Most of the test-applications attached and posted in the bug reports only l=
og
to stdout/stderr. Should I rewrite them and add assertions?=