X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient:	djgpp AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
	bh=7bbv/QoSnGgwoQgZZ+pg3xBnTeYiImzZJWKQ0ZmKriw=;
	b=jw7Kc0WnWEdrJtxYI72cnobKKxwE2WfTilOp7GKcvGCFdPrMicbwL0g1cMFQ0hxcTa
	EYkbTgs1Vvtddj56I+rJVuwInzwIHRDejrqDOUl0dOE37LGPwUeEkxY+4aC/rGiBk4om
	Aenhd/wp3fKjuWrVgbn9yZP0FQsS+XlkW3s3d2y/0Lfxinvj8G4nfPXLF7JwwM6JP3EI
	L4YDT9CXAaqCeTpQGLLfAFe1w3Zqx6Odm4ezFmZc10kRdFozTv8MZ7Y0gIyAJ8/yr1Y0
	f1OflyahO7cpS9pkxEkDqyPKgGh9GzJc5uYB93Y9DKNeePjbRDOyRuwmvtaNuZmBa6KC
	rwzg==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to;
	bh=7bbv/QoSnGgwoQgZZ+pg3xBnTeYiImzZJWKQ0ZmKriw=;
	b=f2XYaLb9DlvCzTbJJkpXjRKutlejfQm758rnVk3IIAHbCwU8w0TbaQzALOLgbwfVCT
	d5U1s9rOV9f1f92v0im26N0afC6vpd2fGUPmo10TB30z0MMlvpulZtlTXXap/ljDP4NS
	2XP58dLYMviP26LwKFybJ3r8h3eikVHcUr/T2kcndELkjk/kRW5C1tKUQpGxPsd1LwVo
	kQZWWjnZAEV+OQwWk8mluMHI3XNV2Oi/E5x7IqBbUZYGFvhdmLCCxSq997J2u7/v1Fq9
	8PufxorfjOFJIbGSbgD4YiK1XQAcn4MZF8uXwuFdZcnqkijfd4vdCqDopDRTlvVHKQPy
	wulA==
X-Gm-Message-State:	ALQs6tC+pCt/CIzixCmifHQ3ecDOtup9gQNMtLcXEaAFcdVmop11vEcN
	GjZ2yopZ+PYuJqIjxVmTKbxmO1cEPCZWj2aB2i3amg==
X-Google-Smtp-Source:	AIpwx4+GDNyn3XwQYNFiIq1msINY+pQQQXxm0a33i/TJqKdAAX9ZybdWCvgdRNwRZapBRs16Mmp5mZd9ayAuJoQt9LY=
X-Received:	by 2002:a24:5085:: with SMTP id m127-v6mr1092976itb.118.1523345594342;
	Tue, 10 Apr 2018 00:33:14 -0700 (PDT)
MIME-Version:	1.0
In-Reply-To:	<b2ce25f9-6861-4a46-8fb9-c0aedd99bf4a@googlegroups.com>
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>
	<b2ce25f9-6861-4a46-8fb9-c0aedd99bf4a AT googlegroups DOT com>
From:	"Ozkan Sezer (sezeroz AT gmail DOT com) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Date:	Tue, 10 Apr 2018 10:33:13 +0300
Message-ID:	<CAA2C=vC0Bydw2gijQMKaUcKyaWGZXFgdB+vvN5GQR5MrQtEQzw@mail.gmail.com>
Subject:	Re: Death of DJGPP support on Win10 32 bit? [WAS: Re: Max value of
	DpmiLimit registry setting in Windows 10 32 bit]
To:	djgpp AT delorie DOT com
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

On 4/10/18, rugxulo AT gmail DOT com [via djgpp AT delorie DOT com] <djgpp AT delorie DOT com> wrote:
> 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)?

I think he means a canadian-cross. i.e. run natively on win32 or
win64 with all tools being win32/or win64 exes, and target djgpp.
E.g.: https://github.com/andrewwutw/build-djgpp.git

- Raw text -