public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gccBug dot 9 dot OkianWarrior at SpamGourmet dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/12245] New: Crashes when compiling large initialized arrays
Date: Thu, 11 Sep 2003 14:50:00 -0000	[thread overview]
Message-ID: <20030911065615.12245.gccBug.9.OkianWarrior@SpamGourmet.com> (raw)

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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

           Summary: Crashes when compiling large initialized arrays
           Product: gcc
           Version: 3.3.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: gccBug dot 9 dot OkianWarrior at SpamGourmet dot com
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: 3.3.1
  GCC host triplet: Linux 2.4.19-16mdk (Mandrake)
GCC target triplet: Linux 2.4.19-16mdk (Mandrake)

This is a simple program with large initialized static arrays (20 arrays of
200,000 elements each, plus a single array with 500,000 elements.

Compiling crashes the compiler after about an hour (900 MHZ system).
Reproduce by typing "Make" (Makefile included).
Actual results are listed below.
Compiling with -Wall shows no warnings.

I really hate to do this to you, but I believe that the problem is related to
initializing very large arrays. Consequently, I cannot generate a small program
which illustrates the problem (and it takes an hour for each experiment, which
doesn't help either). My minimal solution is a C source file of 152 lines
(inconsequential), and two include files of 200,000 lines and 500,000 lines
each. The include files contain initialization data for 21 arrays, and are
nothing more than a list of numbers and commas.

The total source and intermediate files are so BIG that I have not included them
here. I know I'm not supposed to send archives and I'm *really* not supposed to
ask you to download the test cases from the net, but in this instance I think
it's appropriate.

You can get the complete test set (1 source, 2 includes, Makefile, and saved
intermediate file) at www.OkianWarrior.com/gccBug.tar.gz

/home/kibaro/tmp: make
gcc -v -save-temps -o CSolv CSolv.c
Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3.1/specs
Configured with: ./configure
Thread model: posix
gcc version 3.3.1
 /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3.1/cc1 -E -quiet -v -D__GNUC__=3
-D__GNUC_MINOR__=3 -D__GNUC_PATCHLEVEL__=1 CSolv.c CSolv.i
ignoring nonexistent directory "NONE/include"
ignoring nonexistent directory "/usr/local/i686-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
 /usr/local/include
 /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3.1/include
 /usr/include
End of search list.
 /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.3.1/cc1 -fpreprocessed CSolv.i
-quiet -dumpbase CSolv.c -auxbase CSolv -version -o CSolv.s
GNU C version 3.3.1 (i686-pc-linux-gnu)
        compiled by GNU C version 3.2 (Mandrake Linux 9.0 3.2-1mdk).
GGC heuristics: --param ggc-min-expand=47 --param ggc-min-heapsize=32119
gcc: Internal error: Killed (program cc1)
Please submit a full bug report.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
make: *** [CSolv] Error 1


             reply	other threads:[~2003-09-11  6:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-11 14:50 gccBug dot 9 dot OkianWarrior at SpamGourmet dot com [this message]
2003-09-11 15:53 ` [Bug c/12245] " pinskia at gcc dot gnu dot org
2003-09-11 19:26 ` barrabas at barrabas dot mv dot com
2003-09-11 19:28 ` barrabas at barrabas dot mv dot com
2003-09-17  5:14 ` pinskia at gcc dot gnu dot org
2003-09-17  5:18 ` barrabas at barrabas dot mv dot com
2003-09-17  5:25 ` pinskia at gcc dot gnu dot org
2003-10-01  3:33 ` pinskia at gcc dot gnu dot org
2003-10-01  3:35 ` pinskia at gcc dot gnu dot org
2003-10-05  6:32 ` pinskia at gcc dot gnu dot org
2003-11-22 20:39 ` pinskia at gcc dot gnu dot org
2004-01-19 12:57 ` pinskia at gcc dot gnu dot org
2004-05-26 22:38 ` pinskia at gcc dot gnu dot org
2004-09-12 15:36 ` falk at debian dot org
2004-12-02 15:43 ` pinskia at gcc dot gnu dot org
2004-12-02 15:53 ` [Bug c/12245] [3.4.3/4.0.0 regression] Uses lots of memory " ian at wasabisystems dot com
2004-12-02 15:59 ` [Bug c/12245] [3.3/3.4/4.0 " pinskia at gcc dot gnu dot org
2004-12-02 16:10 ` pinskia at gcc dot gnu dot org
2005-01-06  1:22 ` rth at gcc dot gnu dot org
2005-07-22 18:45 ` [Bug c/12245] [3.4/4.0/4.1 " pinskia at gcc dot gnu dot org
2005-07-25  1:30 ` pinskia at gcc dot gnu dot org
2005-07-25  1:34 ` pinskia at gcc dot gnu dot org
2005-09-12  8:55 ` rguenth at gcc dot gnu dot org
2005-09-12 10:03 ` rguenth at gcc dot gnu dot org
2005-09-12 10:10 ` giovannibajo at libero dot it

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=20030911065615.12245.gccBug.9.OkianWarrior@SpamGourmet.com \
    --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).