X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
X-Recipient: djgpp-workers AT delorie DOT com
Message-ID: <514EADD8.3080902@iki.fi>
Date: Sun, 24 Mar 2013 09:40:08 +0200
From: Andris Pavenis <andris DOT pavenis AT iki DOT fi>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: About new DJGPP v2.04 beta
References: <5140A042 DOT 9050805 AT iki DOT fi>
In-Reply-To: <5140A042.9050805@iki.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

On 03/13/2013 05:50 PM, Andris Pavenis wrote:
> I guess we should make a new DJGPP v2.04 beta soon
> and most likely do a release also sometimes
> in not too far future
>
> Some examples where it could be needed:
> - use of upcoming gcc-4.8.0 (changes for
>    1 header file needed, already in CVS)
> - GMP-5.1.X does not compile without trunc()
>    which was recently added to CVS. Really only
>    'make check' fails, but one cannot relay
>    that library will work OK without that
>
> There will most likely be no ports of these
> for DJGPP v2.03.
>
> for gcc-4.8.0: something seems to be broken
> with bash-2.0.4 which prevents building GCC
> for DJGPP v2.03. Unfortunately bash-2.0.5b from
> beta also cannot be used in this case.

One thing I would like to see in DJGPP v2.04 is
nmalloc. It has been used in DJGPP port of GCC
already for long time as DJGPP v2.04 own free()
would make GCC unusably slow.

My another todays message gives another example
where I suspected gcc-4.8.0 at first, but slow
free() was the reason of problem as linking with
nmalloc fixed the problem.

Andris