X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient:	djgpp AT delorie DOT com
Message-ID:	<55406800.4060108@iki.fi>
Date:	Wed, 29 Apr 2015 08:11:28 +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:	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> <553FC4F0 DOT 9080203 AT iki DOT fi>
In-Reply-To:	<553FC4F0.9080203@iki.fi>
Reply-To:	djgpp AT delorie DOT com

On 04/28/2015 08:35 PM, Andris Pavenis wrote:
> 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.

I applied patch changing to nmalloc.
- old memeory managment sources are preserved just not built
- one should additionally update copyright notices as old contact address is unusable for known reasons

Some additional testing is perhaps needed now

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

I'll do it later

Andris

- Raw text -