From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [patch] libstdc++/68276 and libstdc++68995 qualification in <functional>
Date: Tue, 12 Jan 2016 19:40:00 -0000 [thread overview]
Message-ID: <20160112193949.GC30323@redhat.com> (raw)
In-Reply-To: <20151221130212.GZ5356@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 491 bytes --]
On 21/12/15 13:02 +0000, Jonathan Wakely wrote:
>Two patches to add missing std:: qualification to prevent ADL
>problems. Both are regressions, 68276 only on trunk, but 68995 has
>been broken since 4.8.0 (but only affects people mixing TR1 with
>C++11, and I was already rude about them in Bugzilla so won't do it
>again here ;-)
For the branches I added a better test for 68995, this extends the
test on trunk to match what's on the branches now.
Tested x86_64-linux, committed to trunk.
[-- Attachment #2: patch.txt --]
[-- Type: text/x-patch, Size: 823 bytes --]
commit 574125855cb79becc19ed564040a0ca1b23ebabc
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Tue Jan 12 19:19:02 2016 +0000
Extend std::function test for PR 68995
* testsuite/20_util/function/68995.cc: Test reference_wrapper cases.
diff --git a/libstdc++-v3/testsuite/20_util/function/68995.cc b/libstdc++-v3/testsuite/20_util/function/68995.cc
index 78712d6..5690657 100644
--- a/libstdc++-v3/testsuite/20_util/function/68995.cc
+++ b/libstdc++-v3/testsuite/20_util/function/68995.cc
@@ -25,3 +25,8 @@
std::tr1::shared_ptr<int> test() { return {}; }
std::function<std::tr1::shared_ptr<int>()> func = test;
+std::function<std::tr1::shared_ptr<int>()> funcr = std::ref(test);
+
+void test2(std::tr1::shared_ptr<int>) { }
+
+std::function<void(std::tr1::shared_ptr<int>)> func2 = std::ref(test2);
prev parent reply other threads:[~2016-01-12 19:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 13:02 Jonathan Wakely
2015-12-21 13:14 ` Jonathan Wakely
2016-01-12 19:40 ` 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=20160112193949.GC30323@redhat.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).