public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org
To: comer@mailru.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: c++/6273: GCC 2.95.3-5 prints internal error.
Date: Fri, 12 Apr 2002 18:20:00 -0000	[thread overview]
Message-ID: <20020413012015.8813.qmail@sources.redhat.com> (raw)

Synopsis: GCC 2.95.3-5 prints internal error.

State-Changed-From-To: open->analyzed
State-Changed-By: rodrigc
State-Changed-When: Fri Apr 12 18:20:13 2002
State-Changed-Why:
    Compiling with gcc 3.1 results in the following compiler
    error:
    
    main.cpp: In instantiation of `TableMap<int>':
    main.cpp:18:   instantiated from here
    main.cpp:6: Internal compiler error in tree_low_cst, at tree.c:3471
    Please submit a full bug report,
    with preprocessed source if appropriate.
    See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
    
    
    If I compile with:
    g++ -Wall -pedantic-errors main.cpp
    
    I get:
    
    main.cpp: In instantiation of `TableMap<int>':
    main.cpp:18:   instantiated from here
    main.cpp:9: ISO C++ forbids variable-size array
    main.cpp:6: confused by earlier errors, bailing out
    
    
    You can work around this problem by changing:
    
    int items[Index_max+1];
    
    to:
    
    int items[Index_max];
    
    
    This is a problem in gcc that should be fixed.

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


             reply	other threads:[~2002-04-13  1:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-12 18:20 rodrigc [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-12  6:26 comer

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=20020413012015.8813.qmail@sources.redhat.com \
    --to=rodrigc@gcc.gnu.org \
    --cc=comer@mailru.com \
    --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).