From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 37F203840C04; Tue, 9 Jun 2020 18:56:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 37F203840C04 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1591729004; bh=XqqglWdc1foHM5M62roh/3zU+0p9k5aDqeBAG5I0s0U=; h=From:To:Subject:Date:In-Reply-To:References:From; b=j1RSJoeifld72oVLekrXpwmBpANBVkVwa2ioozMWfsFw/y+rBZZ8EPdK1ZI45U7dj 9WrcmyAypPnWa6qK5OR3+PWvdxaUvPkHWyWtCRwvh/PtfGNsiTKqJFPJhlG4d0WPOJ qzux9u/z0jWaTaQFOO29LvIDu7vq3xTeL89UyFBQ= From: "iains at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95615] [coroutines] Coroutine frame and promise is leaked if exception thrown from promise.initial_suspend() Date: Tue, 09 Jun 2020 18:56:44 +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.1.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: iains 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: 10.2 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cf_reconfirmed_on target_milestone everconfirmed bug_status 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: Tue, 09 Jun 2020 18:56:44 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95615 Iain Sandoe changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2020-06-09 Target Milestone|--- |10.2 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Iain Sandoe --- thanks for the report. I think the get-return-object case should now be handled (once the patch to= add the cleanup is approved), since that can be covered by a conventional clean= up expression. Will need to look at the best way to handle the other two.=