public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Daniel Berlin" <dberlin@dberlin.org>
To: gcc-bugzilla@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: [Bug java/29587] jc1: out of memory allocating 4072 bytes after a total of 708630224 bytes
Date: Sat, 04 Nov 2006 17:45:00 -0000	[thread overview]
Message-ID: <4aca3dc20611040945hde1aa71wab5ab7a4eb66f9c7@mail.gmail.com> (raw)
In-Reply-To: <20061104154736.10600.qmail@sourceware.org>

>
> The change on the 19th caused a significant increase in memory
> consumption <http://gcc.gnu.org/ml/gcc-patches/2006-10/msg01029.html>
> and java bootstrap failures on s390, s390x and ia64.  See this
> thread <http://gcc.gnu.org/ml/gcc-patches/2006-10/msg01058.html>.

Except that all of these were fixed in the followup patch and a later
typo fix, *including* the memory usage (see honza's tester).


  reply	other threads:[~2006-11-04 17:45 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 [this message]
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

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=4aca3dc20611040945hde1aa71wab5ab7a4eb66f9c7@mail.gmail.com \
    --to=dberlin@dberlin.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-bugzilla@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).