This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: how small can gcc get?
- From: Dale Johannesen <dalej at apple dot com>
- To: Mike Stump <mrs at apple dot com>
- Cc: gcc at gcc dot gnu dot org, Dale Johannesen <dalej at apple dot com>, Philip George <invest at juun dot com>
- Date: Sun, 24 Apr 2005 09:59:09 -0700
- Subject: Re: how small can gcc get?
- References: <D0524577-B4C6-11D9-8A68-003065BDF310@apple.com>
On Apr 24, 2005, at 6:43 AM, Mike Stump wrote:
On Saturday, April 23, 2005, at 05:05 PM, Philip George wrote:
What's the smallest size I can squeeze gcc down to and how would I go
about compiling it in such a way?
My take:
#define optimize 0
"optimize" is a variable and "int 0" won't parse, so that won't come
close.
What did you really mean?
Turning off optimization is not going to get you the smallest code
size, since many
optimizations reduce it...the option intended to produce smallest code
is -Os. Configuring with --disable-checking is also important.
and then rebuild with dead code stripping. :-) You'd be the first to
do this that I know of, so, won't necessarily be easy, but, might be a
bit smaller than you'd get otherwise.