public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/9820: [3.3/3.4 regression] ice in build_baselink (templates)
Date: Mon, 24 Feb 2003 22:46:00 -0000	[thread overview]
Message-ID: <20030224224601.7417.qmail@sources.redhat.com> (raw)

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

From: Janis Johnson <janis187@us.ibm.com>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org,
   gcc-prs@gcc.gnu.org, poschmid@lbl.gov
Cc:  
Subject: Re: c++/9820: [3.3/3.4 regression] ice in build_baselink (templates)
Date: Mon, 24 Feb 2003 14:47:31 -0800

 The submitter says this test case should be valid,  but
 GCC 3.0.4 and the 3.2-branch both report errors.  I was
 planning to hunt for the patch that caused the regression,
 but if there's a test case that ICEs on legal code, I'd prefer
 to use that one.
 
 Output from GCC 3.2.2 20021220 (prerelease) with -w:
 
 9820.C: In instantiation of `IsFunctionT<int>':
 9820.C:23:   instantiated from `IsClassT<int>'
 9820.C:23:   instantiated from `void check() [with T = int]'
 9820.C:29:   instantiated from here
 9820.C:23: no method `IsFunctionT<int>::test<int>'
 9820.C:23: enumerator value for `Yes' not integer constant
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9820
 
 
 


             reply	other threads:[~2003-02-24 22:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24 22:46 Janis Johnson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-11 22:51 jason
2003-03-11 20:16 jason
2003-02-25 20:46 Janis Johnson
2003-02-24 23:36 Wolfgang Bangerth
2003-02-24 23:26 Janis Johnson
2003-02-24 23:16 Wolfgang Bangerth
2003-02-24 15:27 bangerth

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=20030224224601.7417.qmail@sources.redhat.com \
    --to=janis187@us.ibm.com \
    --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).