public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95505] [coroutines] ICE assert with get_return_object_on_allocation_failure
Date: Sat, 20 Jun 2020 15:40:49 +0000	[thread overview]
Message-ID: <bug-95505-4-aS4FrpXI1T@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95505-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95505

--- Comment #3 from Iain Sandoe <iains at gcc dot gnu.org> ---
we're also discussing whether there's a good way to make this available
automatically.

clang's current implementation includes <new> unconditionally, which is a
possible solution - I'm not thrilled about blanket inclusion of other library
headers (especially when they are not actually directly used by the including
one).

It's a somewhat odd situation - neither <coroutine> nor (quite likely) the
user's code necessarily overly needs "<new>" .. it's an indirect requirement.

So another possibility is to make the std::no throw_t type available and just
construct a temporary object of that type when doing the lookup.

So the ICE is fixed by diagnosing the issue, and making things 'easier' is on
the TODO (but not part of this PR).

  parent reply	other threads:[~2020-06-20 15:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 16:00 [Bug c++/95505] New: " bruck.michael at gmail dot com
2020-06-04 19:54 ` [Bug c++/95505] " iains at gcc dot gnu.org
2020-06-20 15:14 ` cvs-commit at gcc dot gnu.org
2020-06-20 15:40 ` iains at gcc dot gnu.org [this message]
2020-06-21 19:18 ` cvs-commit at gcc dot gnu.org
2020-06-21 19:52 ` iains at gcc dot gnu.org
2020-06-27 10:45 ` bruck.michael at gmail dot com
2020-06-27 10:50 ` 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-95505-4-aS4FrpXI1T@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).