public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/98118] [coroutines] ICE with coroutine with parameter with non-trivial destructor since r10-6876-gdc192bbdd0442f75 Date: Thu, 14 Jan 2021 11:00:21 +0000 [thread overview] Message-ID: <bug-98118-4-KeqpSn4xdr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98118-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98118 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[10/11 |[coroutines] ICE with |Regression][coroutines] ICE |coroutine with parameter |with coroutine with |with non-trivial destructor |parameter with non-trivial |since |destructor since |r10-6876-gdc192bbdd0442f75 |r10-6876-gdc192bbdd0442f75 | Keywords| |ice-on-valid-code Target Milestone|10.3 |--- --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- So it never worked in a released compiler.
next prev parent reply other threads:[~2021-01-14 11:00 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-03 12:13 [Bug c++/98118] New: [coroutines] ICE with coroutine with parameter with non-trivial destructor xzlsmc at gmail dot com 2020-12-03 12:15 ` [Bug c++/98118] " xzlsmc at gmail dot com 2020-12-03 12:15 ` xzlsmc at gmail dot com 2020-12-03 13:16 ` [Bug c++/98118] [10/11 Regression][coroutines] ICE with coroutine with parameter with non-trivial destructor since r10-6876-gdc192bbdd0442f75 marxin at gcc dot gnu.org 2021-01-14 11:00 ` rguenth at gcc dot gnu.org [this message] 2021-03-05 16:59 ` [Bug c++/98118] [coroutines] " cvs-commit at gcc dot gnu.org 2021-03-13 12:54 ` iains at gcc dot gnu.org 2021-03-22 22:04 ` cvs-commit at gcc dot gnu.org 2021-03-24 12:38 ` iains 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-98118-4-KeqpSn4xdr@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: linkBe 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).