public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "niget.tom at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99575] [coroutines] unexpected move when co_awaiting a nonmoveable object
Date: Fri, 24 Mar 2023 12:27:11 +0000 [thread overview]
Message-ID: <bug-99575-4-ELrS5YWeo4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99575-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99575
Tom Niget <niget.tom at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |niget.tom at gmail dot com
--- Comment #3 from Tom Niget <niget.tom at gmail dot com> ---
FWIW, the code in Paweł's comment compiles under 12.1 (and doesn't compile
under 11.3). Maybe this can be closed?
next prev parent reply other threads:[~2023-03-24 12:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 13:37 [Bug c++/99575] New: " lemourin at gmail dot com
2021-09-30 19:56 ` [Bug c++/99575] " iains at gcc dot gnu.org
2021-09-30 19:56 ` iains at gcc dot gnu.org
2021-10-02 18:38 ` iains at gcc dot gnu.org
2021-10-03 19:42 ` cvs-commit at gcc dot gnu.org
2022-06-28 10:43 ` jakub at gcc dot gnu.org
2023-03-24 12:27 ` niget.tom at gmail dot com [this message]
2023-07-07 9:31 ` 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-99575-4-ELrS5YWeo4@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).