Date:	Mon, 10 Sep 2001 14:46:13 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	pavenis AT lanet DOT lv
cc:	sandmann AT clio DOT rice DOT edu, djgpp-workers AT delorie DOT com,
	ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De
Subject:	Re: gcc-301 difficulty
In-Reply-To:	<3B9CA58B.21353.20AB69@localhost>
Message-ID:	<Pine.SUN.3.91.1010910144238.20241E-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 10 Sep 2001 pavenis AT lanet DOT lv wrote:

> On 8 Sep 2001 at 21:18, Eli Zaretskii wrote:
> 
> > > From: "Juan Manuel Guerrero" <ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De>
> > > Organization: Darmstadt University of Technology
> > > Date: Sat, 8 Sep 2001 19:29:49 +0200
> > > 
> > Andris, what significant changes were introduced into GCC between v3.0
> > and 3.0.1?  (I mean not only DJGPP-specific changes.)
> 
> I'm afraid some details have been forgotten from initial posts (correct me Juan, if I'm wrong somewhere):
> 
> this crashes occur with one type of Cyrix CPU and motherboard when
> CPU internal cache is enabled, so one can suspect problem with either
> CPU or motherboard or their incompatibility. It is not the first time one is getting problems with GCC and 
> some Cyrix CPU's (see
> http://www.BitWizard.nl/sig11/ for details)
> 
> It didn't happen with gcc30b.zip from v2gnu/alphas
> 
> It didn't happen with one of my builds of gcc-3.0.1 where I errorously linked cc1 with current CVS libc 
> (as I remeber because I have lost corresponding message from Juan) and reappeared when 
> I linked cc1.exe with modified djdev203.

This last details I didn't remember.  I was under the impression that 
GCC 3.0.1 always triggers these crashes, and that GCC 3.0 never did.

> gcc301b.zip were linked with libc.a from a slightly modified djdev203.zip (only Win2k related fixes). I 
> don't exactly know which exactly GCC (or EGCS) version was used to build most object files from libc 
> (Perhaps Eli or DJ could remeber)

djdev203 was built with GCC 2.8.1.

> Perhaps it would be best to avoid this problem, by using a combination which doesn't trigger that bug. I'm 
> afraid it could be too difficult to find exact reason of problem though.

Yes, it might be hard to find the reason.

> Maybe I should build entire djdev203.zip with gcc-2.95.3 and see
> whether it changes anything 

A good idea, IMHO.

- Raw text -