This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
RE: What can cause a "Memory fault"
- From: Hamilton Chris-cham <chris dot hamilton at freescale dot com>
- To: "'corey taylor'" <corey dot taylor at gmail dot com>, Ian Lance Taylor <ian at airs dot com>
- Cc: Hamilton Chris-cham <chris dot hamilton at freescale dot com>, gcc-help at gcc dot gnu dot org
- Date: Tue, 29 Mar 2005 10:06:45 -0700
- Subject: RE: What can cause a "Memory fault"
I've never been able to get any compiler built on this AMD platform. For bootstrap compiler, I've tried using another compiler I built on a 32-bit Linux platform (not this AMD platform), and I've also tried the compiler that was distributed with this AMD machine.
I haven't read a lot about bad RAM, but I had the impression that if you had bad RAM, your failures wouldn't be so predictable. In my case, the failure happens predictably at the same spot every time (assuming I don't change the configuration).
How can I prove whether this is a memory problem?
Chris
> -----Original Message-----
> From: corey taylor [mailto:corey.taylor@gmail.com]
> Sent: Tuesday, March 29, 2005 10:45 AM
> To: Ian Lance Taylor
> Cc: Hamilton Chris-cham; gcc-help@gcc.gnu.org
> Subject: Re: What can cause a "Memory fault"
>
>
> Chris,
>
> Correct me if I'm wrong, but when we first talked, weren't you able
> to compile a bootstrap at some point and only compiling 3.4.3 was
> causing issues?
>
> corey
>
>
> On 29 Mar 2005 11:39:33 -0500, Ian Lance Taylor <ian@airs.com> wrote:
> > corey taylor <corey.taylor@gmail.com> writes:
> >
> > > This user's question yesterday explains the issue in more detail:
> > >
> > > http://gcc.gnu.org/ml/gcc-help/2005-03/msg00251.html
> >
> > Thanks.
> >
> > That does look more like bad RAM than a compiler bug. It could
> > possibly be a ksh bug or a linker bug.
> >
> > Ian
> >
>