public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ljrittle@gcc.gnu.org
To: daveturgeon@catholic.org, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: c/10321: CC internal error
Date: Fri, 11 Apr 2003 22:27:00 -0000	[thread overview]
Message-ID: <20030411222710.19324.qmail@sources.redhat.com> (raw)

Synopsis: CC internal error

State-Changed-From-To: feedback->closed
State-Changed-By: ljrittle
State-Changed-When: Fri Apr 11 22:27:10 2003
State-Changed-Why:
    Thank you for posting the preprocessed code.  I can compile it with
    GNU C version 3.2.2 (i386-portbld-freebsd4.7) &
    GNU C version 3.2.2 [FreeBSD] 20030205 (release) (i386-undermydesk-freebsd) [as installed on FreeBSD 5.x]
    
    The example required >64MB of memory to compile.  Does your
    machine have enough swap configured?
    The exact error message you reported is indicative of out-of-memory
    (check /var/log/messages for a message that looks like:
    Apr  3 21:14:19 latour /kernel: pid 74396 (cc1), uid 22303, was killed: out of swap space)
    
    You will have to consult FreeBSD documentation on how to configure
    more swap.  This is not a gcc problem other than it is not reported
    as well as it used to be (gcc 2 used to explicitly report that it was
    out of vm, etc.)

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10321


             reply	other threads:[~2003-04-11 22:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-11 22:27 ljrittle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-11 23:56 David Turgeon
2003-04-07 14:35 bangerth
2003-04-06 18:36 daveturgeon

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=20030411222710.19324.qmail@sources.redhat.com \
    --to=ljrittle@gcc.gnu.org \
    --cc=daveturgeon@catholic.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --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).