public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Cc: "Arsen Arsenović" <arsen@aarsen.me>
Subject: [committed] libstdc++: Add missing <bits/stl_algobase.h> include to <bitset>
Date: Fri, 30 Sep 2022 14:46:20 +0100	[thread overview]
Message-ID: <20220930134620.106589-1-jwakely@redhat.com> (raw)

From: Arsen Arsenović <arsen@aarsen.me>

Tested x86_64-linux. Pushed to trunk.

-- >8 --

libstdc++-v3/ChangeLog:

	* include/std/bitset: Include <bits/stl_algobase.h>.
---
 libstdc++-v3/include/std/bitset | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/libstdc++-v3/include/std/bitset b/libstdc++-v3/include/std/bitset
index 1a551cf9785..3fe8b18735c 100644
--- a/libstdc++-v3/include/std/bitset
+++ b/libstdc++-v3/include/std/bitset
@@ -46,6 +46,8 @@
 
 #include <bits/functexcept.h>   // For invalid_argument, out_of_range,
                                 // overflow_error
+#include <bits/stl_algobase.h>  // For std::fill
+
 #if _GLIBCXX_HOSTED
 # include <string>
 # include <iosfwd>
-- 
2.37.3


                 reply	other threads:[~2022-09-30 13:46 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=20220930134620.106589-1-jwakely@redhat.com \
    --to=jwakely@redhat.com \
    --cc=arsen@aarsen.me \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@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).