public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r12-7778] libstdc++: Disable atomic wait for freestanding [PR105021] Date: Wed, 23 Mar 2022 10:11:51 +0000 (GMT) [thread overview] Message-ID: <20220323101151.671273858405@sourceware.org> (raw) https://gcc.gnu.org/g:5bf59b004808abf6acbfe5ef54a0f9216b8dce22 commit r12-7778-g5bf59b004808abf6acbfe5ef54a0f9216b8dce22 Author: Jonathan Wakely <jwakely@redhat.com> Date: Tue Mar 22 21:17:01 2022 +0000 libstdc++: Disable atomic wait for freestanding [PR105021] We use either condition variables or futexes to implement atomic waits, so we can't do it in freestanding. This is non-conforming, so should be revisited later, probably by making freestanding atomic waiting operations spin without ever blocking. Reviewed-by: Thomas Rodgers <trodgers@redhat.com> libstdc++-v3/ChangeLog: PR libstdc++/105021 * include/bits/atomic_base.h [!_GLIBCXX_HOSTED]: Do not include <bits/atomic_wait.h> for freestanding. Diff: --- libstdc++-v3/include/bits/atomic_base.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libstdc++-v3/include/bits/atomic_base.h b/libstdc++-v3/include/bits/atomic_base.h index d86766cf39b..2cad8486c69 100644 --- a/libstdc++-v3/include/bits/atomic_base.h +++ b/libstdc++-v3/include/bits/atomic_base.h @@ -37,7 +37,7 @@ #include <bits/atomic_lockfree_defines.h> #include <bits/move.h> -#if __cplusplus > 201703L +#if __cplusplus > 201703L && _GLIBCXX_HOSTED #include <bits/atomic_wait.h> #endif
reply other threads:[~2022-03-23 10:11 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220323101151.671273858405@sourceware.org \ --to=redi@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@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).