* Build configuration for most compact output
@ 2004-05-08 0:25 John Gonzaga
2004-05-11 4:29 ` llewelly
0 siblings, 1 reply; 2+ messages in thread
From: John Gonzaga @ 2004-05-08 0:25 UTC (permalink / raw)
To: gcc-help
I'm trying to reduce code size and I'm wondering besides the
optimizations flags, what combination of other flags, either in
building the toolchain or command line, that will result in the most
compact output. No dead code, no debug info, etc, just the code that is
required to do the operation of my application. Thanks.
-John G-
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Build configuration for most compact output
2004-05-08 0:25 Build configuration for most compact output John Gonzaga
@ 2004-05-11 4:29 ` llewelly
0 siblings, 0 replies; 2+ messages in thread
From: llewelly @ 2004-05-11 4:29 UTC (permalink / raw)
To: John Gonzaga; +Cc: gcc-help
John Gonzaga <jgonzaga@pnicorp.com> writes:
> I'm trying to reduce code size and I'm wondering besides the
> optimizations flags, what combination of other flags, either in
> building the toolchain or command line, that will result in the most
> compact output. No dead code, no debug info, etc, just the code that
> is required to do the operation of my application. Thanks.
-ffunction-sections --gc-sections *may* help. (It doesn't always help,
so do some experiments.)
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-05-11 4:29 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-05-08 0:25 Build configuration for most compact output John Gonzaga
2004-05-11 4:29 ` llewelly
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).