Xref: news2.mv.net comp.os.msdos.djgpp:3281
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: V2 vs. 1.12m5
Date: Mon, 29 Apr 1996 13:50:28 CDT
Organization: Rice University, Houston, Texas
Lines: 16
Message-ID: <31850f74.sandmann@clio.rice.edu>
References: <31854B53 DOT 1C71 AT goliat DOT eik DOT bme DOT hu>
Reply-To: sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host: clio.rice.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

> So my question really is this: What are the differences between the compilers 
> in V1.12 and in V2 that can cause different behaviour with the same source? 

They are different GCC versions with different optimization options by default.
You can use the V1.12 CC1.EXE with V2 (save, rename, etc) to see if your
problems are mostly V2 based or GCC version based.

> When can I expect a corrected CWSDPMI, with which I can allocate and 
> deallocate as many times I like?

I am currently too busy to cut another release, but ftp.neosoft.com:
pub/users/s/sandmann/csdpmi1heapfix.zip contains a fix for cwsdpmi.
You can also completely avoid the problem by including crt0.h in your
main module and setting the unixy sbrk flag.  Since there are multiple
workarounds, getting the fix out is relatively low priority for me at
this point.