Date:	Mon, 30 Jan 1995 08:27:15 -0800
From:	John Lazenby <john AT sqi DOT com>
To:	eliz AT is DOT elta DOT co DOT il
Subject:	Re: GCC crashes in XMS mode
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu

Sorry, I just got 1.12m3 and only resubscribed to this (high volume)
mailing list when gcc kept hanging.  What is the best way to 
get gcc to not hang?  Will "emm386 ram" work?

> From djgpp-bounces AT sun DOT soe DOT clarkson DOT edu Mon Jan 30 04:25:00 1995
> To: dj AT ctron DOT com
> Cc: djgpp AT sun DOT soe DOT clarkson DOT edu
> Subject: GCC crashes in XMS mode
> Date: Mon, 30 Jan 95 10:42:20 +0200
> From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
> X-Mts: smtp
> 
> A number of users reported recently that gcc 2.6.3 with 1.12m3
> hangs when not running in VCPI or DPMI mode.  Testing on my
> system reveals that this happens both in raw extended memory
> (plain vanilla DOS system) and XMS (plain vanilla system with
> HIMEM.SYS installed) modes.  The following is the relevant
> info I could gather:
> 
>   * GCC.EXE is the one which crashes.  It either hangs the
>     system completely (need a cold reboot) or reboots it.
>     CC1.EXE runs OK in these modes.
> 
>   * When ``topline'' is put into GO32 env var, the top screen
>     line shows that at the moment of crash the address of last
>     syscall/page fault is 0x0000c209, and the amount of used
>     physical RAM is around 130K.
> 
>   * Real-mode GCC.EXE runs OK inder the same circumstances.
> 
> The above was tested on a 486DX2-66 with 16 MBytes of RAM and
> 400 MBytes of free disk space.
> 
> Another, unrelated problem I found is that the real-mode
> GCC.EXE doesn't like the lib/specs file to be DOS-style text
> file (with CR/LF pairs delimiting lines); DJGPP-compiled
> GCC.EXE doesn't have this behavior.
> 

- Raw text -