X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Received: by 10.55.239.12 with SMTP id j12mr5041698qkk.6.1523319541412;
        Mon, 09 Apr 2018 17:19:01 -0700 (PDT)
X-Received: by 10.31.153.82 with SMTP id b79mr3385275vke.9.1523319541151; Mon,
 09 Apr 2018 17:19:01 -0700 (PDT)
Newsgroups: comp.os.msdos.djgpp
Date: Mon, 9 Apr 2018 17:19:00 -0700 (PDT)
In-Reply-To: <20180406-091036.863.0@neozeed.news.eternal-september.org>
Complaints-To: groups-abuse AT google DOT com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=2602:306:8371:4220:721a:4ff:feb1:8570;
 posting-account=p5rsXQoAAAB8KPnVlgg9E_vlm2dvVhfO
NNTP-Posting-Host: 2602:306:8371:4220:721a:4ff:feb1:8570
References: <xnd0zpwjtr DOT fsf AT delorie DOT com> <c5ddafe3-5a20-79eb-bd9b-1794470021e9 AT iki DOT fi>
 <83sh8c47ey DOT fsf AT gnu DOT org> <e8a9925b-8ed9-9542-51bb-7c153f9573eb AT iki DOT fi>
 <83r2nw44a6 DOT fsf AT gnu DOT org> <20180406-091036 DOT 863 DOT 0 AT neozeed DOT news DOT eternal-september DOT org>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <b2ce25f9-6861-4a46-8fb9-c0aedd99bf4a@googlegroups.com>
Subject: Re: Death of DJGPP support on Win10 32 bit? [WAS: Re: Max value of
 DpmiLimit registry setting in Windows 10 32 bit]
From: "rugxulo AT gmail DOT com [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Injection-Date: Tue, 10 Apr 2018 00:19:01 +0000
Content-Type: text/plain; charset="UTF-8"
Bytes: 2367
Lines: 22
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
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
Precedence: bulk

Hi,

On Friday, April 6, 2018 at 4:10:41 AM UTC-5, neozeed wrote:
> 
> If the NTVDM can't nest properly, isn't it easier to just use
> a Win32 native version of GCC, and keep your CC1/CPP/GAS/LD native?

(I think I misunderstood this comment the first few times that I read it.)

So you're saying use a Win32 (PE/COFF) gcc.exe as frontend with other
.EXEs remaining DJGPP (DOS, MZ/COFF)?

IIRC, that's what they did back in the old days when certain OSes
(OS/2?) had similar problems. E.g. /deleted/v1gnu/gcc263rm.zip
says "gcc-2.6.3 gcc.exe built with tcc, for djgpp". (Okay, not Win32
but 16-bit DOS, still a similar workaround.)

But I don't think that will help us much here because all DJGPP
.EXEs do some proxy stuff to transparently handle really long cmdlines
(beyond normal DOS limits).

So it's probably not immediately compatible, but I don't fully
understand all of the details.