Date: Tue, 8 Jun 1999 11:52:25 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Wigoo <wigoo AT seznam DOT cz>
cc: djgpp AT delorie DOT com
Subject: Re: a fwe question
In-Reply-To: <Version.32.19990607220311.00dccab0@axpsu.fpf.slu.cz>
Message-ID: <Pine.SUN.3.91.990608115211.4197T-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 7 Jun 1999, Wigoo wrote:

> Is there any basic rules to have faster program?

See sections 14.2 and 14.5 of the DJGPP FAQ list for some advice.

> I mean something about
> source code like to use register variables instead of int or *int. 

Modern compilers do that anyway when you compile with optimizations
(use -O2 for DJGPP), and they do it better than you would.

> How to find the size of physical memory,  free physical memory,
> all(physical+virtual) memory and all free memory? 

See section 15.2 of the FAQ, it lists some related functions.

> Is there any chance to see error "Stack overflow" or "Heap overflow"?

Yes.  Actually, the message text is different: stack overflows result
in a crash with either GPF or Stack Fault error, and exhausting the
heap space will cause a NULL ponter to be returned by `malloc'; some
programs catch that and print something like "Virtual memory
exhausted".

> Where can I find the version of my gcc compiler

Type "gcc --version".