public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cnstar9988 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug java/29587] jc1: out of memory allocating 4072 bytes after a total of 708630224 bytes
Date: Fri, 12 Oct 2007 09:56:00 -0000 [thread overview]
Message-ID: <20071012095615.1192.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29587-276@http.gcc.gnu.org/bugzilla/>
------- Comment #19 from cnstar9988 at gmail dot com 2007-10-12 09:56 -------
(In reply to comment #18)
> Created an attachment (id=13090)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13090&action=view) [edit]
> A short java file, known to compile under jikes and NetBeans 5.5
> Simple test file demonstrating the bug
gcc-4.2.2
$ gcc -v
Using built-in specs.
Target: hppa1.1-hp-hpux11.11
Configured with: ../src/configure --build=hppa1.1-hp-hpux11.11
--host=hppa1.1-hp-hpux11.11 --target=hppa1.1-hp-hpux11.11
--prefix=/opt/gcc-4.2.2/ilp32 --with-as=/opt/gcc-4.2.2/ilp32/bin/as
--with-gnu-as --with-ld=/usr/ccs/bin/ld --without-gnu-ld --disable-shared
--disable-nls --enable-threads=posix --enable-languages=c,c++
Thread model: posix
gcc version 4.2.2
I want to build gcj.
jc1: out of memory allocating 4072 bytes after a total of 390681928 bytes
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29587
prev parent reply other threads:[~2007-10-12 9:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 23:07 [Bug java/29587] New: " danglin at gcc dot gnu dot org
2006-10-31 11:06 ` [Bug java/29587] " r dot emrich at de dot tecosim dot com
2006-10-31 15:39 ` dave at hiauly1 dot hia dot nrc dot ca
2006-11-04 15:47 ` dave at hiauly1 dot hia dot nrc dot ca
2006-11-04 17:45 ` Daniel Berlin
2006-11-04 17:45 ` dberlin at dberlin dot org
2006-11-04 22:07 ` dave at hiauly1 dot hia dot nrc dot ca
2006-11-05 19:16 ` dberlin at gcc dot gnu dot org
2006-11-05 21:22 ` dave at hiauly1 dot hia dot nrc dot ca
2006-11-05 21:48 ` Daniel Berlin
2006-11-05 21:48 ` dberlin at dberlin dot org
2006-11-06 0:43 ` dave at hiauly1 dot hia dot nrc dot ca
2006-11-07 17:40 ` dberlin at dberlin dot org
2006-11-09 17:24 ` Daniel Berlin
2006-11-09 17:24 ` dberlin at dberlin dot org
2006-11-10 15:20 ` dave at hiauly1 dot hia dot nrc dot ca
2006-11-13 2:18 ` dberlin at gcc dot gnu dot org
2006-11-13 2:22 ` dberlin at gcc dot gnu dot org
2006-11-13 2:22 ` dberlin at gcc dot gnu dot org
2006-11-13 2:31 ` dave at hiauly1 dot hia dot nrc dot ca
2006-12-01 1:07 ` chaoyingfu at gcc dot gnu dot org
2007-02-22 3:26 ` van at wdv dot com
2007-10-12 9:56 ` cnstar9988 at gmail dot com [this message]
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=20071012095615.1192.qmail@sourceware.org \
--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).