public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lucdanton at free dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55408] New: ICE for member template definition with non-type variadic parameter
Date: Tue, 20 Nov 2012 07:18:00 -0000	[thread overview]
Message-ID: <bug-55408-4@http.gcc.gnu.org/bugzilla/> (raw)


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55408

             Bug #: 55408
           Summary: ICE for member template definition with non-type
                    variadic parameter
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: lucdanton@free.fr


Created attachment 28740
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28740
Reproducible testcase

$ g++-snapshot --version
g++-snapshot (Debian 20120915-1) 4.8.0 20120915 (experimental) [trunk revision
191353]

When attempting to compile this program:

struct foo {
    template<int*>
    void bar();
};

template<int*...>
void foo::bar() {}

int main()
{
    extern int i;
    foo {}.bar<&i>();
}

GCC complains:

main.cpp: In function 'int main()':
main.cpp:12:21: internal compiler error: Segmentation fault
     foo {}.bar<&i>();
                     ^

Some casual investigating suggests that this happens every time the definition
for a member template is exactly the same as its declaration save for the fact
that a non-type parameter is made variadic. Otherwise, e.g. if the parameter in
question is a type or template parameter in the declaration or if the template
is declared taking int and defined taking long... then GCC correctly reports
that the definition doesn't have a match.


             reply	other threads:[~2012-11-20  7:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-20  7:18 lucdanton at free dot fr [this message]
2012-11-20  8:19 ` [Bug c++/55408] " mpolacek at gcc dot gnu.org
2012-11-20 10:41 ` paolo.carlini at oracle dot com
2021-08-08  6:44 ` pinskia 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-55408-4@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).