public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/100673] [coroutines] Non-template, UDT await_suspend return-type results in ICE. Date: Sun, 03 Oct 2021 19:50:50 +0000 [thread overview] Message-ID: <bug-100673-4-6WTxTQqCh5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100673-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100673 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Iain D Sandoe <iains@gcc.gnu.org>: https://gcc.gnu.org/g:8009c79b64b532d8a0966fe3c6d636369df6e35d commit r12-4101-g8009c79b64b532d8a0966fe3c6d636369df6e35d Author: John Eivind Helset <jehelset@gmail.com> Date: Sat May 22 01:53:22 2021 +0200 coroutines: Fix ICE with an invalid await_suspend type [PR100673]. The reported ICE occurs when an invalid (non-template) type is found as the return for an await_suspend. Fixed by amending build_co_await to ensure that await_suspend return- type is a template-instantiation before checking to see if it is a valid coroutine handle type. Signed-off-by: John Eivind Helset <jehelset@gmail.com> Signed-off-by: Iain Sandoe <iain@sandoe.co.uk> PR c++/100673 gcc/cp/ChangeLog: * coroutines.cc (build_co_await): Guard against NULL await_suspend types. gcc/testsuite/ChangeLog: * g++.dg/coroutines/pr100673.C: New test.
next prev parent reply other threads:[~2021-10-03 19:50 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-19 10:35 [Bug c++/100673] New: " jehelset at gmail dot com 2021-05-22 3:07 ` [Bug c++/100673] " jehelset at gmail dot com 2021-10-01 20:29 ` iains at gcc dot gnu.org 2021-10-01 20:30 ` iains at gcc dot gnu.org 2021-10-02 18:39 ` iains at gcc dot gnu.org 2021-10-03 19:50 ` cvs-commit at gcc dot gnu.org [this message] 2021-12-21 19:38 ` pinskia at gcc dot gnu.org 2023-05-29 15:03 ` jehelset at gmail dot com
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-100673-4-6WTxTQqCh5@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).