public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/51213] [C++11][DR 1170] Access control checking has to be done under SFINAE conditions Date: Wed, 22 Oct 2014 09:01:00 -0000 [thread overview] Message-ID: <bug-51213-4-PCgfz7nDnK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51213-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51213 --- Comment #20 from Paolo Carlini <paolo.carlini at oracle dot com> --- This is already fixed in mainline, though. I'm adding the testcase.
next prev parent reply other threads:[~2014-10-22 8:58 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-18 20:10 [Bug c++/51213] New: " daniel.kruegler at googlemail dot com 2012-04-04 13:56 ` [Bug c++/51213] " paolo.carlini at oracle dot com 2012-04-20 2:10 ` paolo.carlini at oracle dot com 2012-04-27 1:33 ` jyasskin at gcc dot gnu.org 2012-04-27 9:27 ` paolo.carlini at oracle dot com 2012-06-20 19:10 ` redi at gcc dot gnu.org 2012-07-19 1:38 ` jason at gcc dot gnu.org 2012-07-19 2:06 ` jason at gcc dot gnu.org 2012-07-23 21:02 ` daniel.kruegler at googlemail dot com 2012-07-23 23:36 ` paolo.carlini at oracle dot com 2012-07-24 10:35 ` paolo.carlini at oracle dot com 2012-08-02 18:46 ` paolo at gcc dot gnu.org 2012-08-02 19:38 ` paolo.carlini at oracle dot com 2012-08-25 3:31 ` jason at gcc dot gnu.org 2012-08-31 12:58 ` markus at trippelsdorf dot de 2012-09-04 18:51 ` jason at gcc dot gnu.org 2013-06-23 20:28 ` w.shane.grant at gmail dot com 2013-06-23 22:05 ` paolo.carlini at oracle dot com 2014-10-22 5:29 ` mizvekov at gmail dot com 2014-10-22 6:39 ` mizvekov at gmail dot com 2014-10-22 9:01 ` paolo.carlini at oracle dot com [this message] 2014-10-22 9:24 ` paolo.carlini at oracle dot com 2014-10-22 9:30 ` mizvekov at gmail dot com
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-51213-4-PCgfz7nDnK@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: linkBe 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).