cvs.gedasymbols.org/archives/browse.cgi   search  
Mail Archives: djgpp-workers/1998/09/07/05:22:07

Date: Mon, 7 Sep 1998 12:16:42 +0200 (WET)
From: Andris Pavenis <pavenis AT lanet DOT lv>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc: djgpp-workers AT delorie DOT com
Subject: Re: (should be: egcs-1.1a uploaded)
In-Reply-To: <Pine.SUN.3.91.980906123947.20285Q-100000@is>
Message-ID: <Pine.A32.3.91.980907114645.61918A-100000@ieva06.lanet.lv>
MIME-Version: 1.0


On Sun, 6 Sep 1998, Eli Zaretskii wrote:

> 
> On Sat, 5 Sep 1998, Andris Pavenis wrote:
> 
> > -  would it be usefull to modify archive gcc-e11b.zip to provide
> >    exceptions support for djdev201 (this is not needed for djdev202,
> >    and therefore is not included as I compiled it using djdev202)
> 
> IMHO, yes.  I don't think v2.02 is ready for general public use right
> now, and it will take some time until it will be released.  So I think
> a version of EGCS that can be built with v2.01 is a good idea.
> 

I didn't have any crashes (or other problems) with egcs-1.1 compiled using
slightly patched DJDEV202 except of one example that crashes cc1plus
also under Linux (SIGSEGV). egcs-1.0.3 compiles it (also under Linux).
So this problem is not DJGPP specific. As I mentioned in 
redame.djgpp I had to patch 2 things in DJDEV202:

bug in realloc(): caused crashes in cc1.exe in some sources (maybe also
     somewhere else, but I didn't study this more)

ENFILE instead of ENMFILE: caused problem when COMPILER_PATH were specified
in DJGPP.ENV as in DJDEV202

I didn't met any special problems so I think we should try to release it
as it is (compiled using DJDEV202). Only think we should change is to
modify gcc-e11b.zip to have exceptions support with DJDEV201 and
to have replacement of math.h in compiler version specific directory
similary as we had with gcc-2.8.1.

So I suggest that we can release it as it is without rebuilding. I
only need to modify archive gcc-e11b.zip to have support of djdev201.

Tests I did:
	- tests included with C+ libraries
	- building egcs-1.1a itself
	- building patched version of RHIDE-1.4.5 (patches are needed
          as egcs-1.1 gives more warnings as earlier compilers)
        - building my own software (mainly C++)

I began to try to build DJLSR202 with egcs-1.1 but met some problems
as egcs does more strict control of source code and gives warnings
where earlier compiler failed to do this (options -fqual-cast etc.)
I didn't finish building DJLSR202 but when I'll suceed I'll perhaps
send patches I needed.   

> >    If Yes than is it usefull to release it to general users of DJGPP.   
> 
> Yes!  Past experience shows that some nasty problems only pop up on
> machines of those who don't always know what they are doing.  In
> contrast, people who read djgpp-workers usually have their systems
> configured well and thus don't see these problems at all.
> 
That is one of reasons I asked this. When DJGPP port of gcc-2.8.1 were
put in v2gnu/alphas I didn't get any response about possible problems
before it was released (but there were problems)

One more thing. In previous message I also mentioned PGCC. I tried to
build it and was not satisfied with results:
   - libstdcxx.a build with pgcc-1.1a with options -mpentium -O6
     failed many tests (not from testsuite as we don't have port
     of dejagnu) in directories libio/tests and libstdc++/tests.

As the result I returned to egcs-1.1a.


Andris

- Raw text -


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