From: Jonathan Wakely <jwakely@redhat.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
gcc Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: Add attribute to features deprecated in C++17 [PR91260]
Date: Sun, 16 Jan 2022 20:32:45 +0000 [thread overview]
Message-ID: <CACb0b4ks6+QR2ykX1SVyWMv7CWb_POM6PUUhDEE551SSWVC_xw@mail.gmail.com> (raw)
In-Reply-To: <CACb0b4=UVMjXVuf3zZqsLgOjRakpbzPwfxR-hE1g2kyy8Bn5=g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 861 bytes --]
On Fri, 14 Jan 2022 at 11:32, Jonathan Wakely <jwakely@redhat.com> wrote:
>
>
> On Wed, 12 Jan 2022 at 09:34, Jonathan Wakely via Libstdc++ <
> libstdc++@gcc.gnu.org> wrote:
>
>> This passes testing (with -std=gnu++98/11/17/20) but is quite a large
>> patch for this late in stage 3. Does anybody object to doing this now?
>> The bugs it fixes were closed as INVALID because we're not actually
>> *required* to remove these or deprecate them. But users are right to
>> complain about us silently accepting use of things like std::bind1st in
>> C++20 mode. Probably WONTFIX would have been better, and in fact we can
>> fix them (as this patch does). If we don't do this, users will keep
>> reporting bugs about it, but it could wait for stage 1 if needed.
>>
>
> Pushed to trunk.
>
>
And this fix for the g++ tests.
Tested powerpc64le-linux, pushed to trunk.
[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 962 bytes --]
commit bca1c431affee41ecadb7f29d8d65142a73e0ebf
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Fri Jan 14 22:08:16 2022
libstdc++: Ignore deprecated warnings [PR104037]
The std::pointer_to_binary_function utility was deprecated in C++11 and
removed in C++17. Libstdc++ has started to warn about using it, so
suppress the warnings for this test.
gcc/testsuite/ChangeLog:
PR testsuite/104037
* g++.old-deja/g++.robertl/eb43.C: Ad -Wno-deprecated.
diff --git a/gcc/testsuite/g++.old-deja/g++.robertl/eb43.C b/gcc/testsuite/g++.old-deja/g++.robertl/eb43.C
index 90afbe4f190..c54050c3c7a 100644
--- a/gcc/testsuite/g++.old-deja/g++.robertl/eb43.C
+++ b/gcc/testsuite/g++.old-deja/g++.robertl/eb43.C
@@ -5,6 +5,7 @@
// to pointer_to_binary_function, which has an `explicit' constructor.
// { dg-prune-output "note" }
+// { dg-options "-Wno-deprecated" }
#include <vector>
#include <algorithm>
prev parent reply other threads:[~2022-01-16 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 9:32 Jonathan Wakely
2022-01-14 11:32 ` Jonathan Wakely
2022-01-16 20:32 ` Jonathan Wakely [this message]
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=CACb0b4ks6+QR2ykX1SVyWMv7CWb_POM6PUUhDEE551SSWVC_xw@mail.gmail.com \
--to=jwakely@redhat.com \
--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).