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++/106713] [11/12 Regression] Coroutine regression in GCC 11.3.0: if (co_await ...) crashes with a jump to ud2 since r12-3529-g70ee703c479081ac Date: Wed, 19 Oct 2022 07:10:04 +0000 [thread overview] Message-ID: <bug-106713-4-7yUX5vyOHf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106713-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106713 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[11/12/13 Regression] |[11/12 Regression] |Coroutine regression in GCC |Coroutine regression in GCC |11.3.0: if (co_await ...) |11.3.0: if (co_await ...) |crashes with a jump to ud2 |crashes with a jump to ud2 |since |since |r12-3529-g70ee703c479081ac |r12-3529-g70ee703c479081ac Keywords| |C++-coroutines Known to work| |13.0 Priority|P3 |P2 --- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> --- Fixed on trunk I suppose?
next prev parent reply other threads:[~2022-10-19 7:10 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-106713-4@http.gcc.gnu.org/bugzilla/> 2022-08-30 3:00 ` [Bug c++/106713] [11/12/13 " gcc-bugzilla at decltype dot org 2022-09-07 14:47 ` cvs-commit at gcc dot gnu.org 2022-10-19 7:10 ` rguenth at gcc dot gnu.org [this message] 2022-10-19 7:18 ` [Bug c++/106713] [11/12 " arsen at aarsen dot me 2023-03-16 19:46 ` arsen 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-106713-4-7yUX5vyOHf@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).