public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilson at specifixinc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/17118] internal compiler error in pop_scope
Date: Tue, 24 Aug 2004 05:04:00 -0000	[thread overview]
Message-ID: <20040824050409.6812.qmail@sourceware.org> (raw)
In-Reply-To: <20040820074400.17118.jmvanel@free.fr>


------- Additional Comments From wilson at specifixinc dot com  2004-08-24 05:04 -------
Subject: Re:  internal compiler error in pop_scope

jmvanel at free dot fr wrote:
>>------- Additional Comments From pinskia at gcc dot gnu dot org  2004-08-20 15:37 -------
>>I might go out on a limb and say that you have some hardware problems.
> Seriouly, how can I check my hardware ?

The key thing to check is whether the bugs are reproducible.  If you 
type "make bootstrap" 3 times in a row, do you get the exact same 
failure every time?  You don't have to do builds from scratch.  You can 
just try to continue builds from where they failed.

If you get the same failure every time, then this is likely a gcc bug. 
If you get a different failure every time, then it is likely that this 
is either a kernel bug, or a hardware problem.

If you are having sporadic kernel/hardware failures, then you may be 
able to complete a build if you just keep typing "make bootstrap" enough 
times.

This probably isn't the right group to ask about detecting hardware 
problems.  Maybe there is a linux FAQ about this somewhere?  I don't 
know if there are free programs for this.  There are probably commercial 
Windows based products for PCs.  The BIOS might have some memory testing 
stuff.  Trying a stable linux kernel is probably an easier and cheaper 
and safer solution than messing with hardware, so I'd suggest doing that 
first.


-- 


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


  parent reply	other threads:[~2004-08-24  5:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-20  7:44 [Bug bootstrap/17118] New: " jmvanel at free dot fr
2004-08-20  8:02 ` [Bug bootstrap/17118] " pinskia at gcc dot gnu dot org
2004-08-20  8:14 ` jmvanel at free dot fr
2004-08-20  9:06 ` pinskia at gcc dot gnu dot org
2004-08-20 10:11 ` jmvanel at free dot fr
2004-08-20 14:05 ` jmvanel at free dot fr
2004-08-20 15:37 ` pinskia at gcc dot gnu dot org
2004-08-20 16:40 ` jmvanel at free dot fr
2004-08-24  5:04 ` wilson at specifixinc dot com [this message]
2004-08-31  6:00 ` pinskia at gcc dot gnu dot org

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=20040824050409.6812.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).