Message-Id: <199810291328.PAA47342@ieva06.lanet.lv>
From: "Andris Pavenis" <pavenis AT lanet DOT lv>
To: djgpp AT delorie DOT com, dj AT delorie DOT com
Date: Thu, 29 Oct 1998 15:28:14 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: DJGPP 2.02 Beta 981027
CC: Olivier Perron <perron AT art DOT alcatel DOT fr>
In-reply-to: <Pine.GSO.4.05.9810291058270.9449-100000@rtbsci143s>
X-mailer: Pegasus Mail for Win32 (v3.01b)
Reply-To: djgpp AT delorie DOT com

Date sent:      	Thu, 29 Oct 1998 11:00:27 +0100 (MET)
From:           	Olivier Perron <perron AT art DOT alcatel DOT fr>
To:             	djgpp AT delorie DOT com
Subject:        	Re: DJGPP 2.02 Beta 981027
Send reply to:  	djgpp AT delorie DOT com

> I'm resending this message as it seems that the first one did not arrive
> to destination.
> 
> What should we do with the new specs and djgpp.djl files in %DJDIR/lib ?
> I ask this question because installation instructions from gcc-2.8.1 tell
> us:
> 
> "I also recommend remove files 'specs' and 'djgpp.djl' from %DJDIR/lib.
>  Archive gcc281b.zip contains replacement for these files which will
>  go to a different directory %DJDIR/lib/gcc-lib/djgpp/2.81.
>  If You have changed any of these 2 files You can consider to transfer
>  these changes to new files. It is possible to avoid removing these files
>  but don't do this unless You know what You are doing."
> 

DJGPP 2.02 provides correct exceptions handling also without 
additional object file crtf.o (which were needed with DJGPP 2.01 to 
initialize exceptions handling)  which was reason why there were 
need to do such things earlier. So with DJGPP 2.02 You can omit 
these operations.

Therefore I didn't include crtf.o when ported egcs-1.1 as I did it with
DJGPP 2.02 (I used slightly patched alpha-980726, patched 
malloc.c and doserr2e.c) as I built egcs-1.1 for DJGPP last time
when next alpha (980907) was not yet released.

DJ, I hadn't met any serious problems with DJGPP port of egcs-1.1
except 2 known ones:
	- current problems with exceptions (works in not all conditions),
        also -fsjlj-exceptions is broken in egcs-1.1 also in Linux,
        there are even more problems with exceptions when 
        -fomit-frame-pointer is used;
	- Novel related problems that recently were fixed in port of 
        gcc-2.81 (I simply haven't rebuild egcs-1.1 yet)

As the result I think that maybe it is worth to move egcs-1.1 to
beta stage even without rebuilding. I suggest  v2gnu/betas/egcs-1.1
(not 1.1a as there is no source difference between 1.1a and
1.1b). I'm only afraid that DJGPP port of egcs-1.1 will sty in beta 
stage for rather long time (may be wi'll have to wait for egcs-1.1.1
or something similar). But anyway I think it is good enough for beta.

Andris