Date: Tue, 20 Oct 1998 13:11:32 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Robert Hoehne <robert DOT hoehne AT gmx DOT net>
cc: DJGPP Mailing list <djgpp AT delorie DOT com>
Subject: Re: Can't debug (also note for Robert)
In-Reply-To: <362BA1ED.95B7245@gmx.net>
Message-ID: <Pine.SUN.3.91.981020131026.16812I-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com


On Mon, 19 Oct 1998, Robert Hoehne wrote:

> Do you have any hints what options should be en-/disabled
> for such targets? Let say the following:
> 
> - fastest code
> - smallest code
> - developing code
> - releasing code

I'm probably not the best person to give advice for a tool that I
don't use, but here are my $0.02:

I think that in the vast majority of the cases fastest and smallest
are the same with GCC: use -O2.  With EGCS and PGCC, -O6 might be the
fastest and -O2 the smallest, but I don't have enough experience with
these to tell for sure.

Since I think developing and releasing with different options (except
-s) is a bad idea, I think the "release" target should at most add -s, 
and maybe not even that (since some people might want to release software 
with debug info).

So, in my view, it boils down to:

       [ ] SMALLEST CODE
       [ ] FASTEST CODE
       [ ] WITHOUT DEBUG INFO

and the last can be used with both of the first two.