public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ebb9@email.byu.edu
To: gcc-gnats@gcc.gnu.org
Subject: c++/10347: [3.4] tree check ICE in dependent_type_p
Date: Tue, 08 Apr 2003 13:26:00 -0000	[thread overview]
Message-ID: <20030408131730.5318.qmail@sources.redhat.com> (raw)


>Number:         10347
>Category:       c++
>Synopsis:       [3.4] tree check ICE in dependent_type_p
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Tue Apr 08 13:26:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Eric Blake
>Release:        3.4 20030317 (experimental)
>Organization:
>Environment:
System: CYGWIN_98-4.10 eblake 1.3.22(0.78/3/2) 2003-03-18 09:20 i686 unknown unknown Cygwin
host: i686-pc-cygwin
build: i686-pc-cygwin
target: i686-pc-cygwin
configured with: ../gcc/configure --enable-threads=posix --prefix=/home/eblake/gcc-3.4 --enable-shared --enable-languages=c,c++,java --enable-libgcj --with-gcc-version-trigger=/home/eblake/gcc/gcc/version.c --no-create --no-recursion
>Description:
I think the new parser is choking on this use of templates, distilled from the jikes compiler code.
>How-To-Repeat:
$ cat bug.cc
typedef unsigned int size_t;
void * __attribute__((__cdecl__)) memset (void *, int, size_t);

template <typename Key, typename Value>
struct Map
{
    struct Element
    {
        Element* next;
        Key* key;
        Value* value;
    };
    Element** base;
    unsigned hash_size;
    void Resize();
};

template<typename Key, typename Value>
void Map<Key, Value>::Resize()
{
    delete [] base;
    base = (Element**) memset(new Element*[hash_size], 0,
                              hash_size * sizeof(Element*));
}
$ g++ -c bug.cc
bug.cc: In member function `void Map<Key, Value>::Resize()':
bug.cc:23: internal compiler error: tree check: expected class 't', have 'x' (
   tree_list) in dependent_type_p, at cp/pt.c:11407
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2003-04-08 13:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030408131730.5318.qmail@sources.redhat.com \
    --to=ebb9@email.byu.edu \
    --cc=gcc-gnats@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).