public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Paul Jones" <pajones57@hotmail.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/10874: ICE: unrecognized symbol type ""
Date: Tue, 20 May 2003 17:16:00 -0000 [thread overview]
Message-ID: <20030520171601.24871.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/10874; it has been noted by GNATS.
From: "Paul Jones" <pajones57@hotmail.com>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, pajones57@hotmail.com, gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: c++/10874: ICE: unrecognized symbol type ""
Date: Tue, 20 May 2003 17:07:03 +0000
> This compiles just fine for me. What do you mean by your
> statement that it "Does not crash when only the one file is
> compiled"? If you don't provide us with something with which
> we can reproduce the problem, we can't fix it.
>
> If this is something that you _can_ reproduce, can you
> try to check what happens if you omit -pipe from the
> command line? I wouldn't be surprised if this is just a
> kind of out-of-memory problem, and that might be curable
> by not using -pipe.
Thanks for your help. For some reason my swap partition was not enabled, so
it ran out of physical memory (96M). I mounted swap partition and it works
like a charm. Is it possible to have an out of memory error message?
Thanks Again
Paul
_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=features/junkmail
next reply other threads:[~2003-05-20 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 17:16 Paul Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-20 19:36 Wolfgang Bangerth
2003-05-20 19:08 bangerth
2003-05-20 0:37 bangerth
2003-05-19 21:40 pajones57
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=20030520171601.24871.qmail@sources.redhat.com \
--to=pajones57@hotmail.com \
--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).