public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nilsgladitz at gmail dot com" <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: Fri, 14 May 2021 16:21:04 +0000 [thread overview]
Message-ID: <bug-99576-4-uIfEveCHnA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99576-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99576
Nils Gladitz <nilsgladitz at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nilsgladitz at gmail dot com
--- Comment #1 from Nils Gladitz <nilsgladitz at gmail dot com> ---
I am seeing issues with lambdas and coroutines that I can't quite explain yet.
Specifically reference counting objects capture copied (e.g. std::shared_ptr)
seemed to decrease their reference count more often than they should.
Found this issue which didn't quite seem to match but trying Paweł Wegner's
test case I see something that may explain some weirdness (haven't fully
digested the test case or disregarded the possibility that it is my fault
though).
With vanilla gcc 10.2.0 I am seeing what Paweł observed:
START TASK
Foo()
~Foo()
IN LAMBDA
With vanilla 10.3.0 and 11.1.0 I however see the following:
START TASK
Foo()
IN LAMBDA
~Foo()
~Foo()
i.e. the Foo destructor now gets called later but apparently twice
next prev parent reply other threads:[~2021-05-14 16:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 13:54 [Bug c++/99576] New: [coroutines] desctructor " lemourin at gmail dot com
2021-05-14 16:21 ` nilsgladitz at gmail dot com [this message]
2021-05-15 12:31 ` [Bug c++/99576] [coroutines] destructor " nilsgladitz at gmail dot com
2021-06-10 14:14 ` davidledger at live dot com.au
2021-06-23 8:54 ` victor.burckel at gmail dot com
2021-10-01 19:57 ` iains at gcc dot gnu.org
2022-11-25 11:50 ` adrian.perl at web dot de
2022-11-25 15:13 ` iains at gcc dot gnu.org
2022-11-26 16:28 ` adrian.perl at web dot de
2022-11-26 16:40 ` iains at gcc dot gnu.org
2022-11-27 14:24 ` adrian.perl at web dot de
2022-11-27 15:42 ` iains at gcc dot gnu.org
2022-11-27 16:08 ` adrian.perl at web dot de
2022-11-28 19:13 ` adrian.perl at web dot de
2022-11-30 11:47 ` iains at gcc dot gnu.org
2022-11-30 23:38 ` iains at gcc dot gnu.org
2022-12-02 20:54 ` iains at gcc dot gnu.org
2022-12-04 10:41 ` cvs-commit at gcc dot gnu.org
2023-07-07 9:32 ` rguenth at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-99576-4-uIfEveCHnA@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).