X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
X-Recipient: dj AT delorie DOT com
Message-ID: <553FC4F0.9080203@iki.fi>
Date: Tue, 28 Apr 2015 20:35:44 +0300
From: Andris Pavenis <andris DOT pavenis AT iki DOT fi>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: DJ Delorie <dj AT delorie DOT com>, djgpp AT delorie DOT com
Subject: Re: GCC 5.1.0 problem with <dos.h>
References: <mhmgck$ims$1 AT usenet DOT news DOT interia DOT pl> <201504280005 DOT t3S05t2U020439 AT delorie DOT com> <mhnhb8$m7m$1 AT usenet DOT news DOT interia DOT pl> <201504281718 DOT t3SHIpWZ009266 AT envy DOT delorie DOT com>
In-Reply-To: <201504281718.t3SHIpWZ009266@envy.delorie.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

On 04/28/2015 08:18 PM, DJ Delorie wrote:
> Ah, I see.
>
> I see no reason to not spin a 2.05 release just to get this out, but
> the only other issue we've had stopping this is the malloc one.  IIRC
> the last concern I had with changing malloc was breaking the ABI, but
> if Juan and Andris can agree on what malloc "works" we'll just go with
> that and have something that can replace both 2.03 and 2.04.
>
I have used nmalloc to build GCC already for a long time (since gcc-3.4 if I remember correctly)
and I do not remember that there would be too much complaints about quality (v2.03 builds were
less stable, but I have dropped even attempts to build GCC for DJGPP v2.03)

I can apply patch I posted almost a month ago unless there are objections. There are none from
my side.

Committed small fix for dbgcom.c for build using gcc-5.1 (I only tried cross-compiler under Linux)
All other seems to build OK.

We should also "resurrect" rmake.cc used by DJGPP testsuite (some small changes needed)

That would be all from my side

Andris