public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
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:06:00 -0000 [thread overview]
Message-ID: <20010723100601.8145.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR c/2160; it has been noted by GNATS.
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: <anton@mips.complang.tuwien.ac.at>
Cc: <gcc-bugs@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org>
Subject: Re: c/2160: signal 11 when compiling large generated program
Date: Mon, 23 Jul 2001 11:05:32 +0100 (BST)
On Mon, 23 Jul 2001, Anton Ertl wrote:
> > (not sent to gcc-gnats, so not filed with this PR).
>
> Should I do something else than replying to all recipients of your mail?
It needs to go to gcc-gnats@gcc.gnu.org to be filed with the PR. GNATS
status change messages used to include this address in the headers, but it
seems they don't any more. This is a bug in the bug tracking system
configuration.
> > 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
--
Joseph S. Myers
jsm28@cam.ac.uk
next reply other threads:[~2001-07-23 3:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 3:06 Joseph S. Myers [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-25 17:45 rth
2001-07-23 3:16 Anton Ertl
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=20010723100601.8145.qmail@sourceware.cygnus.com \
--to=jsm28@cam.ac.uk \
--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).