X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient:	djgpp AT delorie DOT com
Subject:	Re: Random compile errors under WIndows (32 bit Windows Vista and
	Windows 10)
To:	djgpp AT delorie DOT com
References:	<5611566C DOT 4020507 AT iki DOT fi> <561A4BCE DOT 7050606 AT iki DOT fi>
	<56213FE2 DOT 7090409 AT iki DOT fi> <562168C6 DOT 5050001 AT gmx DOT de>
From:	"Andris Pavenis (andris DOT pavenis AT iki DOT fi) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Message-ID:	<5621D433.2020004@iki.fi>
Date:	Sat, 17 Oct 2015 07:53:07 +0300
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
	Thunderbird/38.3.0
MIME-Version:	1.0
In-Reply-To:	<562168C6.5050001@gmx.de>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On 10/17/2015 12:14 AM, Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) [via djgpp AT delorie DOT com] wrote:
> Please do not get me wrong, I really appreciate your efforts but all of your
> activity seems to imply that this will be again another week-end without the
> release of DJGPP 2.05.
> Are there any realistic chances that we will release DJGPP 2.05 before the end
> of the year?  We are already working for at least 6 months on this.
>
> I really fear that we are again on the road to nowhere like with DJGPP 2.04.
> I gain the impression that we are confusing real impediments, that do not exist
> at all,  with particular features that some developer would like to see implemented
> before this release gets released.  No matter if we are talking about something like
> DXE support or if we are talking about windows 10 support.
>
It is up to us to decide which problems to consider show-stoppers. If gcc developers would try to
completely clean up all known bugs they would never release a single version.

I do not think that instability of GCC preprocessor under WIndows 10 should delay release unless
there are other significant problems. It should however be OK to discuss DJGPP problems when
used under WIndows 10.

We could release DJGPP v2.06 soon enough if really critical problems wuold be found and fixed
soon. That would not require so much efforts as current release due to smaller amount of
changes

About current instability:

- nmalloc problems mentioned earlier are not source. They were present also for Windows Vista
which I used to build GCC packages available on ftp.delorie.com and they did not prevent
me from building GCC. These problems do not appear to be source of difficulties also
under Windows 10

- there seems to be no instability in running some other DJGPP programs. I tried program
for calculating arbitrary number of decimal signs of number pi I mentioned in earlier message.
No problems detected trying to calculate 100000000 decimal signs of pi under Windows 10.
That required near 1GB of DPMI memory and took more than 5 minutes per run.

- random DPMI corruption would much more likely bite actual compiler not preprocessor due to larger
amount of required resources

After all that I'm more inclined to think that the problem lies on our side. There could be slight
differences between different DPMI providers that could trigger problems. I have some more
ideas to try but I would not like to discuss them before trying.

It may also take time to fix the problem if really found.

So guess we should actually release 2.05 now.

Andris

- Raw text -