X-Authentication-Warning:	ieva01.lanet.lv: pavenis owned process doing -bs
Date:	Mon, 17 May 1999 10:05:12 +0300 (WET)
From:	Andris Pavenis <pavenis AT lanet DOT lv>
To:	DJ Delorie <dj AT delorie DOT com>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: gcc 3.0
In-Reply-To:	<199905170522.BAA06889@envy.delorie.com>
Message-ID:	<Pine.A41.4.05.9905170950280.58860-100000@ieva01.lanet.lv>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 17 May 1999, DJ Delorie wrote:

> 
> The egcs team is working towards a code freeze for egcs-1.2 aka
> egcs-2.95 aka pre-gcc-3.0.
> 
> Now would be the time to really work on the few remaining
> djgpp-related bugs in egcs (templates? namespaces?) so that we're
> ready to go as soon as gcc 3.0 is announced, without having to tell
> everyone where the patches are :-(
> 

I think there is no C, C++ and other languages specific patches needed
specially for DJGPP port of egcs. It's so already for port of egcs-1.1.2.
I have not touched these things at all and I'm sure it's not needed.

About templates. There are problems with templates which appears as
unresolved references while linking. Tests shows (according to Mark
Elbrecht) that even -frepo does not fix all problems. Perhaps these
problems should be resolved in binutils but not in gcc. I also not sure
they are only DJGPP specific.

About namespaces. I have not heard about DJGPP specifix problems with 
namespaces in egcs-1.1.2. However I have not tested them.

The problem that must be resolved is building upcomming version for DJGPP
and I expect problems there:
	forcing --prefix=$DJDIR through configure
	scripts and makefiles, it is needed there and we cannot avoid it. 
	Of course we can find some hack to get environment variable
	resolved in other way but I don't think gcc is appropriate place
	where to use such hacks.

Andris

- Raw text -