public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ensadc at mailnesia dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/97700] Bogus error when a class containing a function pointer is used as a non-type template parameter
Date: Tue, 03 Nov 2020 14:21:08 +0000	[thread overview]
Message-ID: <bug-97700-4-RyOuuoQyCV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97700-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97700

ensadc at mailnesia dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=83258

--- Comment #1 from ensadc at mailnesia dot com ---
The lambda is not needed to reproduce the bug. This also triggers the error:

void fun() {}
struct S 
{ 
    void (*f)(); 
}; 

template<S> struct X {};
using x = X<S{ fun }>;

  reply	other threads:[~2020-11-03 14:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03 14:14 [Bug c++/97700] New: " ensadc at mailnesia dot com
2020-11-03 14:21 ` ensadc at mailnesia dot com [this message]
2020-11-19 18:54 ` [Bug c++/97700] " mpolacek at gcc dot gnu.org
2021-03-13 21:42 ` johelegp at gmail dot com
2023-03-17 17:57 ` pinskia at gcc dot gnu.org
2023-05-09 21:23 ` mail at lboeger dot de
2023-05-10 13:13 ` ppalka at gcc dot gnu.org
2023-05-11 14:05 ` cvs-commit at gcc dot gnu.org
2023-05-11 14:25 ` ppalka at gcc dot gnu.org
2023-05-12 15:08 ` cvs-commit at gcc dot gnu.org
2023-05-12 15:25 ` ppalka 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-97700-4-RyOuuoQyCV@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).