This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug bootstrap/17118] internal compiler error in pop_scope


------- 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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]