delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/2001/09/03/08:43:55

Message-ID: <250B3114DA16D511B82C00E0094005F8023FC102@MSGWAW11>
From: =?iso-8859-2?Q?Wojciech_Ga=B3=B1zka?= <wojciech DOT galazka AT polkomtel DOT com DOT pl>
To: "'djgpp-workers AT delorie DOT com'" <djgpp-workers AT delorie DOT com>
Subject: Re gcc301 difficulty
Date: Mon, 3 Sep 2001 14:42:34 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id IAA27207
Reply-To: djgpp-workers AT delorie DOT com


> ----------
> Od: 	Juan Manuel Guerrero[SMTP:ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De]
> Odpowiedz do: 	djgpp-workers AT delorie DOT com
> Wysłano: 	03 wrze¶nia 2001 13:45
> Do: 	pavenis AT lanet DOT lv; Eli Zaretskii
> DW: 	djgpp-workers AT delorie DOT com
> Temat: 	Re: gcc301 difficulty
> 
> The reason for the failure seems to be the processor.
> I am using a system composed by:
> MB:  Tyan Trinity 100AT
> uP:  SGS-Thomson ST6x86 P166+ (FSB 66MHz, CPU Multiplicator: 2x)
> RAM: 32MB (fast page) + 32MB (edo)
> 
> 
You seem to mix EDO and FP RAM  which is a bad idea as they work a bit
differently. Try compiling with only one type of memory (the other one
removed) and try also to tinker a bit with BIOS setting like "Slow refresh
rate" (for a start try to 'load BIOS defaults)
GCC is a complex piece of software and it will always fail if there is a
problem with memory

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019