public inbox for libstdc++-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-5470] libstdc++: Fix circular dependency for bitmap_allocator [PR103381] Date: Tue, 23 Nov 2021 12:58:03 +0000 (GMT) [thread overview] Message-ID: <20211123125803.C51F93858D28@sourceware.org> (raw) https://gcc.gnu.org/g:5459fa132a99e6037e5ccf1b49d617677a584ff8 commit r12-5470-g5459fa132a99e6037e5ccf1b49d617677a584ff8 Author: Jonathan Wakely <jwakely@redhat.com> Date: Tue Nov 23 12:28:22 2021 +0000 libstdc++: Fix circular dependency for bitmap_allocator [PR103381] <ext/bitmap_allocator.h> includes <function>, and since C++17 that includes <unordered_map>. If std::allocator is defined in terms of __gnu_cxx::bitmap_allocator then you get a circular reference and bootstrap fails when compiling src/c++17/*.cc. libstdc++-v3/ChangeLog: PR libstdc++/103381 * include/ext/bitmap_allocator.h: Include <bits/stl_function.h> instead of <functional>. Diff: --- libstdc++-v3/include/ext/bitmap_allocator.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libstdc++-v3/include/ext/bitmap_allocator.h b/libstdc++-v3/include/ext/bitmap_allocator.h index cc80593764c..0444deb479c 100644 --- a/libstdc++-v3/include/ext/bitmap_allocator.h +++ b/libstdc++-v3/include/ext/bitmap_allocator.h @@ -31,7 +31,7 @@ #include <utility> // For std::pair. #include <bits/functexcept.h> // For __throw_bad_alloc(). -#include <functional> // For greater_equal, and less_equal. +#include <bits/stl_function.h> // For greater_equal, and less_equal. #include <new> // For operator new. #include <debug/debug.h> // _GLIBCXX_DEBUG_ASSERT #include <ext/concurrence.h>
reply other threads:[~2021-11-23 12:58 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=20211123125803.C51F93858D28@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).