From: Douglas Richardson <douglas.richardson@gaussvip.com>
To: 'Chris Croswhite' <ccroswhite@get2chip.com>, gcc-help@gcc.gnu.org
Subject: RE: Executable size
Date: Wed, 25 Sep 2002 10:57:00 -0000 [thread overview]
Message-ID: <AA067AE32DECD511B8A00002555878BC161F6E@mailsrv2.magellan.com> (raw)
Chris,
Are you using any optimizations? How are you linking with the runtime
libraries?
Send the output of gcc -v.
Douglas Richardson.
-----Original Message-----
From: Chris Croswhite [mailto:ccroswhite@get2chip.com]
Sent: Wednesday, September 25, 2002 10:55
To: gcc-help@gcc.gnu.org
Subject: Executable size
Sirs,
I am trying to figure out how to reduce the size of my executable (that
has grown with the increments of gcc upgrades even though the code base
has not changed). I would like to understand how I can reduce/cut out
so that the executable to back down to the 2.953 size. Can anyone give
me some pointers?
TIA,
Chris
next reply other threads:[~2002-09-25 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 10:57 Douglas Richardson [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-21 3:47 Mike Rejsa
2023-01-21 13:16 ` NightStrike
2002-09-25 11:34 Douglas Richardson
2002-09-25 10:55 Chris Croswhite
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AA067AE32DECD511B8A00002555878BC161F6E@mailsrv2.magellan.com \
--to=douglas.richardson@gaussvip.com \
--cc=ccroswhite@get2chip.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).