public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Denis dot Excoffier at airbus dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/29087]  New: More than 35000 switch cases crash cc1plus
Date: Thu, 14 Sep 2006 17:38:00 -0000	[thread overview]
Message-ID: <bug-29087-12787@http.gcc.gnu.org/bugzilla/> (raw)

the exact version of GCC is 4.1.1
the system type is sparc-sun-solaris2.8
the options given when GCC was configured/built:
  --prefix=/tmp/local/unixutil/gcc-4.1.1
  --with-local-prefix=/usr/local/myCompanyName
  ("myCompanyName" is not the exact wording)
  (also, there is a symlink /tmp/local/unixutil/gcc -> gcc-4.1.1)
the complete command line that triggers the bug:
  gcc -Wall -o foo.o -c foo.cc
the compiler output (error messages, warnings, etc.):
  stdout: nothing
  stderr:
    gcc: Internal error: Segmentation Fault (program cc1plus)
    Please submit a full bug report.
    See <URL:http://gcc.gnu.org/bugs.html> for instructions.
  foo.o: not created
the preprocessed file:
  see below; for ease of transmission, the full source is not given;
  to have it, replace the ZZZZZ by the missing 65524 values (in
  increasing order)
additional remarks:
  1) if the file is renamed foo.c (the C language is triggered instead
     of C++), the bug does not show up
  2) if the command is installed in a Makefile:
---Makefile--------------------------
all:
        /tmp/local/unixutil/gcc/bin/gcc -Wall -o foo.o -c foo.cc
-------------------------------------
     then the bug does not show up if the GNU make is used, however the bug
     still shows up if the /usr/ccs/bin/make is used


---foo.ii----------------------------
# 1 "foo.cc"
# 1 "<built-in>"
# 1 "<command line>"
# 1 "foo.cc"
void myfunction(unsigned short localChar) {
  switch (localChar) {
    case 0:
    case 1:
    case 2:
    case 3:
    case 4:
    case 5:
ZZZZZ
    case 65530:
    case 65531:
    case 65532:
    case 65533:
    case 65534:
    case 65535:
      break;
  };
  return;
};
-------------------------------------


-- 
           Summary: More than 35000 switch cases crash cc1plus
           Product: gcc
           Version: 4.1.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: Denis dot Excoffier at airbus dot com
 GCC build triplet: sparc-sun-solaris2.8
  GCC host triplet: sparc-sun-solaris2.8
GCC target triplet: sparc-sun-solaris2.8


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29087


             reply	other threads:[~2006-09-14 17:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14 17:38 Denis dot Excoffier at airbus dot com [this message]
2006-09-15  8:26 ` [Bug c++/29087] [4.1/4.2 Regression] " rguenth at gcc dot gnu dot org
2006-09-15 15:23 ` steven at gcc dot gnu dot org
2006-09-15 16:24 ` steven at gcc dot gnu dot org
2006-09-15 21:01 ` steven at gcc dot gnu dot org
2006-09-15 21:23 ` steven at gcc dot gnu dot org
2006-09-15 23:48 ` steven at gcc dot gnu dot org
2006-09-16 17:40 ` patchapp at dberlin dot org
2006-09-18 15:33 ` steven at gcc dot gnu dot org
2006-09-18 15:42 ` [Bug c++/29087] [4.1 " steven at gcc dot gnu dot org
2006-09-21 20:28 ` steven at gcc dot gnu dot org
2006-09-21 21:32 ` steven at gcc dot gnu dot org
2006-09-21 21:33 ` steven at gcc dot gnu dot org

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=bug-29087-12787@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).