public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "debian-gcc at lists dot debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/19004] New: [3.4 / 4.0 regression] ICE in uses_template_parms at cp/pt.c:4860
Date: Wed, 15 Dec 2004 10:40:00 -0000	[thread overview]
Message-ID: <20041215104032.19004.debian-gcc@lists.debian.org> (raw)

[forwarded from http://bugs.debian.org/284777]

seen with 3.4 branch 20041215 and CVS HEAD, works with 3.3 CVS branch

$ g++-3.4 bug-284777.cc
bug-284777.cc: In member function `void Dummy<T>::tester()':
bug-284777.cc:13: internal compiler error: in uses_template_parms, at cp/pt.c:4860
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.

template<typename T>
struct Dummy
{
  void evil()
  {
    this->template tester<true>();
  }
	    
  template<bool B>
  void tester()
  {
    // evil should actually be a bool  
    bar<evil>()();
  }
  template<bool B>
  struct bar
  {
    void operator()()
    { }
  };
};

int main()
{}

-- 
           Summary: [3.4 / 4.0 regression] ICE in uses_template_parms at
                    cp/pt.c:4860
           Product: gcc
           Version: 3.4.4
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: debian-gcc at lists dot debian dot org
                CC: gcc-bugs at gcc dot gnu dot org


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


             reply	other threads:[~2004-12-15 10:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-15 10:40 debian-gcc at lists dot debian dot org [this message]
2004-12-15 11:00 ` [Bug c++/19004] " debian-gcc at lists dot debian dot org
2004-12-15 12:04 ` [Bug c++/19004] [3.4/4.0 " steven at gcc dot gnu dot org
2004-12-15 13:45 ` pinskia at gcc dot gnu dot org
2004-12-15 15:30 ` lerdsuwa at gcc dot gnu dot org
2004-12-16 14:55 ` lerdsuwa at gcc dot gnu dot org
2004-12-16 15:07 ` lerdsuwa at gcc dot gnu dot org
2004-12-18  3:52 ` pinskia at gcc dot gnu dot org
2004-12-23 16:39 ` reichelt at gcc dot gnu dot org
2005-02-02  1:45 ` [Bug c++/19004] " reichelt at gcc dot gnu dot org
2005-02-02  1:46 ` reichelt at gcc dot gnu dot org
2005-02-23 15:01 ` reichelt at gcc dot gnu dot org
2005-02-23 15:04 ` reichelt at gcc dot gnu dot org
2005-04-16 22:04 ` pinskia at gcc dot gnu dot org
2005-07-15 21:40 ` [Bug c++/19004] [3.4/4.0/4.1 Regression] " pinskia at gcc dot gnu dot org
2005-07-22 21:16 ` pinskia at gcc dot gnu dot org
2005-08-25 22:49 ` mmitchel at gcc dot gnu dot org
2005-08-26 19:38 ` cvs-commit at gcc dot gnu dot org
2005-08-26 19:39 ` mmitchel at gcc dot gnu dot org
2005-08-26 19:42 ` cvs-commit at gcc dot gnu dot org
2005-08-26 21:08 ` [Bug c++/19004] [3.4 " pinskia at gcc dot gnu dot org
2005-09-02 13:40 ` reichelt at gcc dot gnu dot org
2005-09-03 19:53 ` cvs-commit at gcc dot gnu dot org
2005-09-03 19:59 ` reichelt at gcc dot gnu dot 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=20041215104032.19004.debian-gcc@lists.debian.org \
    --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).