public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libcc1/105695] GCC 10.3.1 (20220519) build failure with GCC 12
Date: Mon, 23 May 2022 08:34:12 +0000	[thread overview]
Message-ID: <bug-105695-4-VfZO3urpQ5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105695-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105695

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #2)
> <algorithm> is required pre C++11 for std::swap.

Right, it got moved to <utility> for C++11. GCC 10 uses C++98 so needs
<algorithm> for std::swap.

As noted at https://gcc.gnu.org/gcc-12/porting_to.html both <utility> and
<algorithm> are less widely used inside libstdc++, so you are less likely to
get those headers transitively by including other library headers.

  parent reply	other threads:[~2022-05-23  8:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-22 22:12 [Bug libcc1/105695] New: " sam at gentoo dot org
2022-05-22 22:23 ` [Bug libcc1/105695] " pinskia at gcc dot gnu.org
2022-05-23  8:01 ` rguenth at gcc dot gnu.org
2022-05-23  8:34 ` redi at gcc dot gnu.org [this message]
2024-06-15  6:09 ` sjames 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-105695-4-VfZO3urpQ5@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: 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).