X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date: Tue, 18 Dec 2001 21:48:34 +0200 (WET)
From: Andris Pavenis <pavenis AT lanet DOT lv>
X-Sender: pavenis AT ieva06
To: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Cc: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Subject: Re: GCC build with 2.03 refresh OK (Win2K, WinXP) - Ready for ?
In-Reply-To: <10112161725.AA20038@clio.rice.edu>
Message-ID: <Pine.A41.4.05.10112182144310.24980-100000@ieva06>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk



On Sun, 16 Dec 2001, Charles Sandmann wrote:

> Andris's binaries were built on the 2.03 refresh patches - we're talking
> about the same binaries.  I just ran the sample problem on Win95 using
> the 3.02 binaries (from Simtel) which are a test for the 2.03 refresh -
> and I did not have any problem with the compile.
> 
> I don't believe the problem quoted in the newgroup (which is a week old
> with no other feedback from the author) is a refresh problem - more likely
> a Windows 95 memory configuration problem straight out of the FAQ.
> 
> Now, I can get almost the exact same error in W95 by limiting the amount
> of DPMI memory to 14336Kb.  So it takes 15Mb to compile a null program
> with GPP 3.02.  What does it take to convince you guys this isn't a 
> refresh issue?  Give me break.
> 

Didn't test gcc-3.0.2 now, but gcc-3.1 20011205 (experimental) compiles
simple C or C++ program with only one printf in DOS session with 
only 7 Mb DPMI memory. Using 'std::cout << "Hello" << std::endl;"
instead in C++ increases minimal memory to about 16 Mb (failure
with 12 Mb). Tests done under Win95 OSR2. 

Andris