public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Giovanni Bajo" <giovannibajo@libero.it>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/10223: template trickery causes ICE (segmentation fault)
Date: Fri, 02 May 2003 17:36:00 -0000	[thread overview]
Message-ID: <20030502173601.24998.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/10223; it has been noted by GNATS.

From: "Giovanni Bajo" <giovannibajo@libero.it>
To: <gcc-gnats@gcc.gnu.org>,
	<hg211@ural2.hszk.bme.hu>,
	<gcc-bugs@gcc.gnu.org>,
	<nobody@gcc.gnu.org>,
	<gcc-prs@gcc.gnu.org>
Cc:  
Subject: Re: c++/10223: template trickery causes ICE (segmentation fault)
Date: Fri, 2 May 2003 19:28:29 +0200

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10223
 
 Not really related to c++/9364 (as shown by my recent analysys of that PR).
 Instead, an epurated code snippet of this PR looks this way:
 --------------------------------------------
 template <typename T>
 struct Foo
 {
     template <void (T::*)()>
     struct dummy;
 
     template <typename Q>
     static char test(dummy<&Q::whatever> *);
 };
 
 
 struct Bar {};
 
 template struct Foo<Bar>;
 //template struct Foo<int>;
 --------------------------------------------
 pr10223.cpp: In instantiation of `Foo<Bar>':
 pr10223.cpp:14:   instantiated from here
 pr10223.cpp:8: internal compiler error: Segmentation fault
 Please submit a full bug report,
 
 If you instantiate the template with a basic type instead of Bar (using the
 commented line instead of the other one), we get an ICE on error recovery:
 
 pr10223.cpp: In instantiation of `Foo<int>':
 pr10223.cpp:15:   instantiated from here
 pr10223.cpp:5: error: creating pointer to member function of non-class type
 `int'
 pr10223.cpp:5: internal compiler error: in retrieve_specialization, at
 cp/pt.c:894
 Please submit a full bug report,
 
 I keep both the ICEs in this same PR since they are very likely related.
 Reconfirmed on every GCC version I have (2.95 -> mainline CVS 20030430).
 
 After this redux has been fixed, I suggest trying again the original code
 provided by the poster, which could reveal other problems.
 
 Giovanni Bajo
 


             reply	other threads:[~2003-05-02 17:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-02 17:36 Giovanni Bajo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-27 21:56 Volker Reichelt
2003-03-26 15:28 bangerth
2003-03-26 14:56 hg211

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=20030502173601.24998.qmail@sources.redhat.com \
    --to=giovannibajo@libero.it \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).