public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth 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:01:52 +0000 [thread overview]
Message-ID: <bug-105695-4-XjMmY789rj@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
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2022-05-23
Keywords| |build
Ever confirmed|0 |1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Indeed.
#include <utility>
void foo (void *a, void *b)
{
std::swap (a, b);
}
> ~/install/gcc-12/usr/local/bin/g++ t.C -S -std=gnu++03
t.C: In function 'void foo(void*, void*)':
t.C:5:8: error: 'swap' is not a member of 'std'
5 | std::swap (a, b);
| ^~~~
works with GCC 11. <algorithm> is required pre C++11 for std::swap. We
have
#ifdef __cplusplus
#if defined (INCLUDE_ALGORITHM) || !defined (HAVE_SWAP_IN_UTILITY)
# include <algorithm>
#endif
but config.h was likely generated with the default C++ standard and not with
explicit -std=gnu++98.
next prev parent reply other threads:[~2022-05-23 8:01 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 [this message]
2022-05-23 8:34 ` redi at gcc dot gnu.org
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-XjMmY789rj@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).