From: Jakub Jelinek <jakub@redhat.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Thomas Rodgers <rodgert@appliantology.com>,
David Edelsohn <dje.gcc@gmail.com>,
gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: GCC 11.1 Release Candidate available from gcc.gnu.org
Date: Thu, 22 Apr 2021 14:30:40 +0200 [thread overview]
Message-ID: <20210422123040.GQ1179226@tucnak> (raw)
In-Reply-To: <20210422122740.GC3008@redhat.com>
On Thu, Apr 22, 2021 at 01:27:40PM +0100, Jonathan Wakely wrote:
> I'm just finishing testing this on various targets and will push to
> trunk. I'd like to backport it to gcc-11 too, to fix PR100179.
Ok for 11.1.
> commit 50070d8602a07160cece5890899929e9f210244d
> Author: Jonathan Wakely <jwakely@redhat.com>
> Date: Thu Apr 22 11:10:06 2021
>
> libstdc++: Remove #error from <semaphore> implementation [PR 100179]
>
> This removes the #error from <bits/semaphore_base.h> for the case where
> neither __atomic_semaphore nor __platform_semaphore is defined.
>
> Also rename the _GLIBCXX_REQUIRE_POSIX_SEMAPHORE macro to
> _GLIBCXX_USE_POSIX_SEMAPHORE for consistency with the similar
> _GLIBCXX_USE_CXX11_ABI macro that can be used to request an alternative
> (ABI-changing) implementation.
>
> libstdc++-v3/ChangeLog:
>
> PR libstdc++/100179
> * include/bits/semaphore_base.h: Remove #error.
> * include/std/semaphore: Do not define anything unless one of
> the implementations is available.
Jakub
prev parent reply other threads:[~2021-04-22 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210420152439.GR1179226@tucnak>
[not found] ` <CAGWvnykjEBYoK=poyfSWy84Eix__GJ-NJ50QSc99ji-UM8n+Wg@mail.gmail.com>
[not found] ` <6ac731c557415b46b04613d9b908df2f@appliantology.com>
[not found] ` <CAGWvnymcuXzvrBEm6rrTvXzRyoCYgx0vUm2nUBMWA29aQZc4uQ@mail.gmail.com>
[not found] ` <a69622f7cc24e6e311d5099b9899e798@appliantology.com>
[not found] ` <CAGWvnykWuuxtDKen5AXfX5k__UsChmvJAhp5-vC6O5LFnhqjBQ@mail.gmail.com>
[not found] ` <CAGWvnykNJ0VqcMcFfBrQUTTFOk_J2PVj2Ci5jNZu55sbnc7Y9w@mail.gmail.com>
[not found] ` <45de03629a536c0000c9b47bb79d6601@appliantology.com>
2021-04-21 8:56 ` Jakub Jelinek
2021-04-21 9:05 ` Jonathan Wakely
2021-04-21 11:38 ` Jonathan Wakely
2021-04-21 12:12 ` Jonathan Wakely
2021-04-21 14:16 ` Thomas Rodgers
2021-04-21 14:23 ` David Edelsohn
2021-04-21 14:30 ` Jonathan Wakely
2021-04-22 12:27 ` Jonathan Wakely
2021-04-22 12:30 ` Jakub Jelinek [this message]
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=20210422123040.GQ1179226@tucnak \
--to=jakub@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=rodgert@appliantology.com \
/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).