public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: scamel@inf.elte.hu
To: gcc-gnats@gcc.gnu.org
Subject: c++/8615: internal compiler error
Date: Fri, 22 Nov 2002 13:23:00 -0000	[thread overview]
Message-ID: <20021117203451.8184.qmail@sources.redhat.com> (raw)


>Number:         8615
>Category:       c++
>Synopsis:       internal compiler error
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Sun Nov 17 12:36:02 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     scamel@inf.elte.hu
>Release:        3.2.1-pre6 20021111 Debian-prerelease
>Organization:
>Environment:
Celeron 366 with Asus P2B-F motherboard, Debian sid
>Description:
Compiler crashes when compiling a simple source. It's not perfectly legal code, but I think it should compile. The command line and compiler output is:


~/work/cpp$ g++-3.2 -v proba.cc -save-temps
Reading specs from /usr/lib/gcc-lib/i386-linux/3.2.1/specs
Configured with: /home/packages/gcc/3.2/gcc-3.2-3.2.1ds5/src/configure -v --enable-languages=c,c++,java,f77,proto,objc,ada --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.2 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-java-gc=boehm --enable-objc-gc i386-linux
Thread model: posix
gcc version 3.2.1 20021111 (Debian prerelease)
 /usr/lib/gcc-lib/i386-linux/3.2.1/cpp0 -lang-c++ -D__GNUG__=3 -D__DEPRECATED -D__EXCEPTIONS -v -D__GNUC__=3 -D__GNUC_MINOR__=2 -D__GNUC_PATCHLEVEL__=1 -D__GXX_ABI_VERSION=102 -D__ELF__ -Dunix -D__gnu_linux__ -Dlinux -D__ELF__ -D__unix__ -D__gnu_linux__ -D__linux__ -D__unix -D__linux -Asystem=posix -D__NO_INLINE__ -D__STDC_HOSTED__=1 -D_GNU_SOURCE -Acpu=i386 -Amachine=i386 -Di386 -D__i386 -D__i386__ -D__tune_i386__ proba.cc proba.ii
GNU CPP version 3.2.1 20021111 (Debian prerelease) (cpplib) (i386 Linux/ELF)
ignoring nonexistent directory "/usr/i386-linux/include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/include/c++/3.2
 /usr/include/c++/3.2/i386-linux
 /usr/include/c++/3.2/backward
 /usr/local/include
 /usr/lib/gcc-lib/i386-linux/3.2.1/include
 /usr/include
End of search list.
 /usr/lib/gcc-lib/i386-linux/3.2.1/cc1plus -fpreprocessed proba.ii -quiet -dumpbase proba.cc -version -o proba.s
GNU CPP version 3.2.1 20021111 (Debian prerelease) (cpplib) (i386 Linux/ELF)
GNU C++ version 3.2.1 20021111 (Debian prerelease) (i386-linux)
        compiled by GNU C version 3.2.1 20021111 (Debian prerelease).
proba.cc:4: Internal compiler error in tree_low_cst, at tree.c:3484
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
>How-To-Repeat:
template <class CharType, CharType line_terminator = 0>
class String {};

String<char, 255> s;
>Fix:
If 255 is replaced with a value between -128..127, the code compiles. I think code is legal and 255 should be converted to signed char as usual, but I'm not sure.
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2002-11-17 20:36 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=20021117203451.8184.qmail@sources.redhat.com \
    --to=scamel@inf.elte.hu \
    --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).