public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Anton Ertl <anton@a0.complang.tuwien.ac.at>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c/2160: signal 11 when compiling large generated program
Date: Mon, 23 Jul 2001 03:16:00 -0000	[thread overview]
Message-ID: <20010723101601.10568.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR c/2160; it has been noted by GNATS.

From: Anton Ertl <anton@a0.complang.tuwien.ac.at>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c/2160: signal 11 when compiling large generated program
Date: Mon, 23 Jul 2001 12:12:53 +0200 (MET DST)

 [This is a copy of a message already sent to
 anton@mips.complang.tuwien.ac.at, gcc-bugs@gcc.gnu.org,
 gcc-prs@gcc.gnu.org, jsm28@cam.ac.uk, nobody@gcc.gnu.org]
 
 jsm28@gcc.gnu.org wrote:
 >     Feedback at http://gcc.gnu.org/ml/gcc-bugs/2001-06/msg01531.html
 >     (not sent to gcc-gnats, so not filed with this PR).
 
 Should I do something else than replying to all recipients of your mail?
 
 >     Excess memory consumption is still a bug; changed from
 >     ice-on-legal-code to sw-bug.
 
 I finally managed to compile this file on an Alpha with 1GB with
 gcc-3.0 with
 
 gcc -mieee -c engine.i
 
 Top showed about 1550MB virtual memory consumption during most of the
 time.  Top showed that the CPU was mostly in system or idle mode, with
 only about 0.5% user time; took about 30 hours.  The compiler produced
 a file engine.o, so I assume the compilation went ok (unfortunately I
 was not smart enough to log the output and status).
 
 - anton
 
 


             reply	other threads:[~2001-07-23  3:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-23  3:16 Anton Ertl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-25 17:45 rth
2001-07-23  3:06 Joseph S. Myers
2001-07-20 14:17 jsm28
2001-06-22  5:09 jsm28

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=20010723101601.10568.qmail@sourceware.cygnus.com \
    --to=anton@a0.complang.tuwien.ac.at \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).