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 libstdc++/94973] compile error when trying to use pointer-to-member function as invokable projection to ranges::find() Date: Wed, 06 May 2020 15:24:51 +0000 [thread overview] Message-ID: <bug-94973-4-SWyKGQro29@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94973-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94973 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2020-05-06 Ever confirmed|0 |1 Status|UNCONFIRMED |WAITING --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- Please read https://gcc.gnu.org/bugs and provide the missing information. Why is this marked as a libstdc++ bug?
next prev parent reply other threads:[~2020-05-06 15:24 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-06 15:03 [Bug libstdc++/94973] New: " db0451 at gmail dot com 2020-05-06 15:24 ` redi at gcc dot gnu.org [this message] 2020-05-06 15:40 ` [Bug libstdc++/94973] " redi at gcc dot gnu.org 2020-05-06 15:48 ` db0451 at gmail dot com 2020-05-06 15:50 ` db0451 at gmail dot com 2020-05-06 16:03 ` [Bug c++/94973] " redi at gcc dot gnu.org 2020-05-06 16:04 ` redi at gcc dot gnu.org 2020-05-06 16:16 ` redi at gcc dot gnu.org 2020-05-06 16:17 ` db0451 at gmail dot com 2020-05-06 16:18 ` redi at gcc dot gnu.org 2020-05-06 16:26 ` redi at gcc dot gnu.org 2020-05-06 16:27 ` redi at gcc dot gnu.org 2020-05-06 16:30 ` redi at gcc dot gnu.org 2020-05-06 16:32 ` rguenth at gcc dot gnu.org 2020-05-06 16:39 ` redi at gcc dot gnu.org 2020-05-06 16:42 ` db0451 at gmail dot com 2020-05-06 16:46 ` db0451 at gmail dot com 2020-05-06 16:47 ` redi 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-94973-4-SWyKGQro29@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).