public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/15414] New: Failure in compiling very huge C program
@ 2004-05-13 14:46 gprizzi at tin dot it
  2004-05-13 14:49 ` [Bug c/15414] " falk at debian dot org
                   ` (5 more replies)
  0 siblings, 6 replies; 7+ messages in thread
From: gprizzi at tin dot it @ 2004-05-13 14:46 UTC (permalink / raw)
  To: gcc-bugs

Dear sirs

I am working with Politecnico of Milano on a project for ESA.
I have a problem and I hope you can kindly suggest me a way to solve it.

I got a failure in compiling a very big C source code, automatically generated 
by a tool for dynamic multi body simulation.
The source file is 21 MB and the preprocessed file is about 14 Mb in size.

The output of the compiler is the following:
cc1: Cannot allocate 4228939388 bytes after allocating 14476768 bytes
 /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/cpp0 -lang-c -v -I. -
I/root/dymola/source -D__GNUC__

I am working on an Intel work station with:
PIV 3Ghz
1 GB RAM
Linux operting system - slackware 9.1
Gcc version 3.2.3

The command line I used for the compilation is the following:

gcc -v -save-temps -o dymosim -O -DDYMOSIM -DUNIX -DSkip_f2c_UNDEFS -I. -
I/root/dymola/source 
dsmodel.c /root/dymola/source/dymosim.c /root/dymola/bin/libds.a /root/dymola/bi
n/librtai.a -lm -lcomedi >logs.txt 2>&1

and the following is the output of the command:

Reading specs from /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/specs
Configured with: ../gcc-3.2.3/configure --prefix=/usr --enable-shared --enable-
threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld --verbose -
-target=i486-slackware-linux --host=i486-slackware-linux
Thread model: posix
gcc version 3.2.3
 /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/cpp0 -lang-c -v -I. -
I/root/dymola/source -D__GNUC__=3 -D__GNUC_MINOR__=2 -D__GNUC_PATCHLEVEL__=3 -
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__OPTIMIZE__ -D__STDC_HOSTED__=1 -Acpu=i386 -Amachine=i386 -Di386 -D__i386 -
D__i386__ -D__tune_i486__ -DDYMOSIM -DUNIX -DSkip_f2c_UNDEFS dsmodel.c dsmodel.i
GNU CPP version 3.2.3 (cpplib) (i386 Linux/ELF)
ignoring nonexistent directory "/usr/i486-slackware-linux/include"
#include "..." search starts here:
#include <...> search starts here:
 .
 /root/dymola/source
 /usr/local/include
 /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/include
 /usr/include
End of search list.
 /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/cc1 -fpreprocessed dsmodel.i -
quiet -dumpbase dsmodel.c -O -version -o dsmodel.s
GNU CPP version 3.2.3 (cpplib) (i386 Linux/ELF)
GNU C version 3.2.3 (i486-slackware-linux)
	compiled by GNU C version 3.2.3.
In file included from /root/dymola/source/matrixop.h:36,
                 from dsmodel.c:11:
/root/dymola/source/dsutil.h:486: warning: static declaration for `remainder' 
follows non-static

cc1: Cannot allocate 4228939388 bytes after allocating 14476768 bytes
 /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/cpp0 -lang-c -v -I. -
I/root/dymola/source -D__GNUC__=3 -D__GNUC_MINOR__=2 -D__GNUC_PATCHLEVEL__=3 -
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__OPTIMIZE__ -D__STDC_HOSTED__=1 -Acpu=i386 -Amachine=i386 -Di386 -D__i386 -
D__i386__ -D__tune_i486__ -DDYMOSIM -DUNIX -
DSkip_f2c_UNDEFS /root/dymola/source/dymosim.c dymosim.i
GNU CPP version 3.2.3 (cpplib) (i386 Linux/ELF)
ignoring nonexistent directory "/usr/i486-slackware-linux/include"
#include "..." search starts here:
#include <...> search starts here:
 .
 /root/dymola/source
 /usr/local/include
 /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/include
 /usr/include
End of search list.
 /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/cc1 -fpreprocessed dymosim.i -
quiet -dumpbase dymosim.c -O -version -o dymosim.s
GNU CPP version 3.2.3 (cpplib) (i386 Linux/ELF)
GNU C version 3.2.3 (i486-slackware-linux)
	compiled by GNU C version 3.2.3.
 /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/../../../../i486-slackware-
linux/bin/as -V -Qy -o dymosim.o dymosim.s
GNU assembler version 2.14.90.0.6 (i486-slackware-linux) using BFD version 
2.14.90.0.6 20030820

I have the preprocessed file but how can I sent it to you?

Please can you suggest me how can I get my source code compiled?

Thank you in advance for your help.

Gianpaolo Rizzi
gprizzi@tin.it

-- 
           Summary: Failure in compiling very huge C program
           Product: gcc
           Version: 3.2.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: gprizzi at tin dot it
                CC: gcc-bugs at gcc dot gnu dot org


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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Bug c/15414] Failure in compiling very huge C program
  2004-05-13 14:46 [Bug c/15414] New: Failure in compiling very huge C program gprizzi at tin dot it
@ 2004-05-13 14:49 ` falk at debian dot org
  2004-09-23 13:34 ` [Bug rtl-optimization/15414] " pinskia at gcc dot gnu dot org
                   ` (4 subsequent siblings)
  5 siblings, 0 replies; 7+ messages in thread
From: falk at debian dot org @ 2004-05-13 14:49 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From falk at debian dot org  2004-05-13 09:43 -------
(In reply to comment #0)

> I have the preprocessed file but how can I sent it to you?

Use "Create a New Attachment" at the URL below.

> Please can you suggest me how can I get my source code compiled?

Try turning off optimization, or splitting the file.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING


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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Bug rtl-optimization/15414] Failure in compiling very huge C program
  2004-05-13 14:46 [Bug c/15414] New: Failure in compiling very huge C program gprizzi at tin dot it
  2004-05-13 14:49 ` [Bug c/15414] " falk at debian dot org
@ 2004-09-23 13:34 ` pinskia at gcc dot gnu dot org
  2004-12-02 23:29 ` pinskia at gcc dot gnu dot org
                   ` (3 subsequent siblings)
  5 siblings, 0 replies; 7+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2004-09-23 13:34 UTC (permalink / raw)
  To: gcc-bugs



-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
     Ever Confirmed|                            |1
   Last reconfirmed|0000-00-00 00:00:00         |2004-09-23 13:34:23
               date|                            |


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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Bug rtl-optimization/15414] Failure in compiling very huge C program
  2004-05-13 14:46 [Bug c/15414] New: Failure in compiling very huge C program gprizzi at tin dot it
  2004-05-13 14:49 ` [Bug c/15414] " falk at debian dot org
  2004-09-23 13:34 ` [Bug rtl-optimization/15414] " pinskia at gcc dot gnu dot org
@ 2004-12-02 23:29 ` pinskia at gcc dot gnu dot org
  2005-06-25 13:16 ` steven at gcc dot gnu dot org
                   ` (2 subsequent siblings)
  5 siblings, 0 replies; 7+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2004-12-02 23:29 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-12-02 23:29 -------
We need the preprocessed source of the failing source?
Maybe you could put it up on a web site or an ftp server.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING


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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Bug rtl-optimization/15414] Failure in compiling very huge C program
  2004-05-13 14:46 [Bug c/15414] New: Failure in compiling very huge C program gprizzi at tin dot it
                   ` (2 preceding siblings ...)
  2004-12-02 23:29 ` pinskia at gcc dot gnu dot org
@ 2005-06-25 13:16 ` steven at gcc dot gnu dot org
  2005-07-31  5:36 ` pinskia at gcc dot gnu dot org
  2005-07-31  5:37 ` pinskia at gcc dot gnu dot org
  5 siblings, 0 replies; 7+ messages in thread
From: steven at gcc dot gnu dot org @ 2005-06-25 13:16 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From steven at gcc dot gnu dot org  2005-06-25 13:16 -------
The test case from l8120l.i.bz2 compiles flawlessly with GCC CVS HEAD.  The 
maximum memory footprint I get is 350MB. 
 
Not sure what to do with this bug, I don't see a problem anymore.  Which 
compilers failed, and which succeed? 

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|2004-09-23 13:34:23         |2005-06-25 13:16:51
               date|                            |


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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Bug rtl-optimization/15414] Failure in compiling very huge C program
  2004-05-13 14:46 [Bug c/15414] New: Failure in compiling very huge C program gprizzi at tin dot it
                   ` (3 preceding siblings ...)
  2005-06-25 13:16 ` steven at gcc dot gnu dot org
@ 2005-07-31  5:36 ` pinskia at gcc dot gnu dot org
  2005-07-31  5:37 ` pinskia at gcc dot gnu dot org
  5 siblings, 0 replies; 7+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-07-31  5:36 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 05:17 -------
Hmm, on powerpc-darwin on the mainline, we spike up to 900MB for some reason and then drop back 
down to 400MB.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
 GCC target triplet|                            |powerpc-darwin
   Last reconfirmed|2005-06-25 13:16:51         |2005-07-31 05:17:07
               date|                            |


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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* [Bug rtl-optimization/15414] Failure in compiling very huge C program
  2004-05-13 14:46 [Bug c/15414] New: Failure in compiling very huge C program gprizzi at tin dot it
                   ` (4 preceding siblings ...)
  2005-07-31  5:36 ` pinskia at gcc dot gnu dot org
@ 2005-07-31  5:37 ` pinskia at gcc dot gnu dot org
  5 siblings, 0 replies; 7+ messages in thread
From: pinskia at gcc dot gnu dot org @ 2005-07-31  5:37 UTC (permalink / raw)
  To: gcc-bugs


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-07-31 05:36 -------
The memory is not in GC at all.  I don't which pass is allocating the memory.

-- 


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


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2005-07-31  5:36 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-05-13 14:46 [Bug c/15414] New: Failure in compiling very huge C program gprizzi at tin dot it
2004-05-13 14:49 ` [Bug c/15414] " falk at debian dot org
2004-09-23 13:34 ` [Bug rtl-optimization/15414] " pinskia at gcc dot gnu dot org
2004-12-02 23:29 ` pinskia at gcc dot gnu dot org
2005-06-25 13:16 ` steven at gcc dot gnu dot org
2005-07-31  5:36 ` pinskia at gcc dot gnu dot org
2005-07-31  5:37 ` pinskia at gcc dot gnu dot org

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).