public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jay.krell at cornell dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug spam/45929] New: insn-attrtab.c is too big, can't compile within a few hundred MB (4.3.5 oops)
Date: Thu, 07 Oct 2010 08:26:00 -0000 [thread overview]
Message-ID: <bug-45929-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45929
Summary: insn-attrtab.c is too big, can't compile within a few
hundred MB (4.3.5 oops)
Product: gcc
Version: 4.3.5
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: spam
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: jay.krell@cornell.edu
insn-attrtab.c is too big, can't compile within a few hundred MB
oops, this is 4.3.5, I meant to be building 4.5.1!
bootstrap compiler is I believe:
-bash-4.1$ /usr/sfw/bin/gcc -v
Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs
Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure
--prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as
--with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++
--enable-shared
Thread model: posix
gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)
gcc -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes
-Wmissing-prototypes -Wold-style-definition -Wmissing-format-attribute
-DHAVE_CONFIG_H -I. -I. -I../../gcc/gcc -I../../gcc/gcc/.
-I../../gcc/gcc/../include -I../../gcc/gcc/../libcpp/include
-I/home/jkrell/dev2/cm3/m3-sys/m3cc/AMD64_SOLARIS/./gmp
-I/home/jkrell/dev2/cm3/m3-sys/m3cc/gcc/gmp -I../../gcc/gcc/../libdecnumber
-I../../gcc/gcc/../libdecnumber/dpd -I../libdecnumber insn-attrtab.c -o
insn-attrtab.o
cc1: out of memory allocating 235720640 bytes after a total of 185008128 bytes
gmake: *** [insn-attrtab.o] Error 1
-bash-4.1$ ulimit
unlimited
-bash-4.1$ ulimit -a
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
open files (-n) 256
pipe size (512 bytes, -p) 10
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 16357
virtual memory (kbytes, -v) unlimited
-bash-4.1$ uname -a
SunOS current10x 5.10 Generic_142910-17 i86pc i386 i86pc
next reply other threads:[~2010-10-07 8:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 8:26 jay.krell at cornell dot edu [this message]
2010-10-07 9:03 ` [Bug spam/45929] " jay.krell at cornell dot edu
2010-10-07 9:34 ` rguenth at gcc dot gnu.org
2010-10-07 10:31 ` jay.krell at cornell dot edu
2010-10-07 10:36 ` jakub at gcc dot gnu.org
2011-02-26 14:45 ` rueger at informatik dot hu-berlin.de
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-45929-4@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).