public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ehrhardt@mathematik.uni-ulm.de
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: c++/10722: ICE after "error:   expected a type, got `pm::nothing'"
Date: Wed, 14 May 2003 16:59:00 -0000	[thread overview]
Message-ID: <20030514165908.9842.qmail@sources.redhat.com> (raw)

Synopsis: ICE after "error:   expected a type, got `pm::nothing'"

State-Changed-From-To: open->analyzed
State-Changed-By: cae
State-Changed-When: Wed May 14 16:59:08 2003
State-Changed-Why:
    Reduced testcase for 3.3:
    ============= cut ==========
    template <class  P, class Q>
    struct pair {};
    
    template <typename T>
    struct pair<T, INVALID> {
            typedef T first_type;
    };
    ============= cut ==========
    
    ICE is 3.3-only. 3.4 has a different ICE with the original testcase
    
    Segfault is in constructor_name_full at cp/decl2.c:1240 because
    the parameter thing is NULL.
    
    Reduced testcase for 3.4 is:
    ============= cut ==========
    template <class P> struct spec_object_traits {};
    template <class P, class Q> struct pair {};
    template <typename T1>
    struct spec_object_traits< pair<T1, INVALID> > :
    spec_object_traits<T1> { };
    ============= cut ==========
    
    This is a tree-checking ICE in xref_basetypes at cp/decl.c:12788
    where we need an error_mark check.
    
    
        regards  Christian
    

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10722


             reply	other threads:[~2003-05-14 16:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14 16:59 ehrhardt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-09 21:56 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=20030514165908.9842.qmail@sources.redhat.com \
    --to=ehrhardt@mathematik.uni-ulm.de \
    --cc=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --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).