public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bgoodr+gccbugzilla at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/31502] gcc/g++ randomly seg faults, sometimes freezes the entire machine
Date: Mon, 07 May 2007 03:19:00 -0000	[thread overview]
Message-ID: <20070507031921.16105.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31502-14370@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from bgoodr+gccbugzilla at gmail dot com  2007-05-07 04:19 -------
(In reply to comment #6)
> compiling software always taxes the system more than any thing else as it is
> using more of the CPU time and memory and disk than most other software.  ...

Thanks Andrew.  I'm coming around to that conclusion myself, as I attempted
several times to rebuild from scratch using GCC 3.2.3 "compat" libraries:

gcc32 (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-56.fc5)

and am getting random internal compiler errors again.  My conclusion for now is
that it is not likely to be GCC 4.1.1 at fault.  It might be time for a system
upgrade.

Thanks!
Brent


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31502


      parent reply	other threads:[~2007-05-07  3:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-07 11:45 [Bug c++/31502] New: " ye dot patrick at gmail dot com
2007-04-07 14:31 ` [Bug c++/31502] " pinskia at gcc dot gnu dot org
2007-04-07 14:43 ` ye dot patrick at gmail dot com
2007-04-07 15:29 ` bangerth at dealii dot org
2007-04-08  3:39 ` ye dot patrick at gmail dot com
2007-05-07  1:54 ` bgoodr+gccbugzilla at gmail dot com
2007-05-07  2:00 ` pinskia at gcc dot gnu dot org
2007-05-07  3:19 ` bgoodr+gccbugzilla at gmail dot com [this message]

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=20070507031921.16105.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).