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 libstdc++/107139] Time to remove #if _GLIBCXX_HOSTED guard for coroutine for freestanding
Date: Tue, 04 Oct 2022 14:07:10 +0000	[thread overview]
Message-ID: <bug-107139-4-15QMkMr1bq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107139-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:

https://gcc.gnu.org/g:b74ab7a1609f01afaab9b82cfabfb96ae9e1145d

commit r13-3060-gb74ab7a1609f01afaab9b82cfabfb96ae9e1145d
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Oct 4 09:37:14 2022 +0100

    libstdc++: Enable std::hash<coroutine_handle<P>> [PR107139]

    Everything that <coroutine> depends on is available for freestanding
    now.

    libstdc++-v3/ChangeLog:

            PR libstdc++/107139
            * include/std/coroutine: Remove all _GLIBCXXHOSTED preprocessor
            conditionals.

  reply	other threads:[~2022-10-04 14:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04  0:25 [Bug libstdc++/107139] New: " unlvsur at live dot com
2022-10-04 14:07 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-05 16:04 ` [Bug libstdc++/107139] " unlvsur at live 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-107139-4-15QMkMr1bq@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).