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++/100179] [12 regression] xtreme-header-2_a.H fails on arm-eabi Date: Thu, 22 Apr 2021 13:37:33 +0000 [thread overview] Message-ID: <bug-100179-4-yPgXq2ewfe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100179-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100179 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:718fcebe8b65e98b794f9a53ce7358e034657588 commit r11-8282-g718fcebe8b65e98b794f9a53ce7358e034657588 Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Apr 22 11:10:06 2021 +0100 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. (cherry picked from commit 4b2db8077136d2f8b5a0db026e6161810be327b3)
next prev parent reply other threads:[~2021-04-22 13:37 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-21 11:54 [Bug libstdc++/100179] New: " clyon at gcc dot gnu.org 2021-04-21 11:55 ` [Bug libstdc++/100179] " clyon at gcc dot gnu.org 2021-04-21 14:26 ` redi at gcc dot gnu.org 2021-04-22 12:59 ` cvs-commit at gcc dot gnu.org 2021-04-22 13:37 ` cvs-commit at gcc dot gnu.org [this message] 2021-04-22 13:38 ` redi at gcc dot gnu.org 2021-04-23 8:36 ` clyon at gcc dot gnu.org 2021-04-23 8:41 ` redi 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-100179-4-yPgXq2ewfe@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).