From: Mike Rejsa <mikerejsa@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Executable size
Date: Fri, 20 Jan 2023 22:47:08 -0500 [thread overview]
Message-ID: <C1829EC6-C029-4E85-A6E6-1C46E0FF8870@gmail.com> (raw)
Hi, new to gcc, running 32b on an old Win-XP notebook.
When I compile small utilities (say, treesort or equivalent, just console output) I get executables that are from 10-16 times larger as with my previous compiler (a 16b Aztec). Something that compiles to 7-8k with the Aztec is 100k+ with gcc. Why is this?
TIA
miker
next reply other threads:[~2023-01-21 3:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 3:47 Mike Rejsa [this message]
2023-01-21 13:16 ` NightStrike
-- strict thread matches above, loose matches on Subject: below --
2002-09-25 11:34 Douglas Richardson
2002-09-25 10:57 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=C1829EC6-C029-4E85-A6E6-1C46E0FF8870@gmail.com \
--to=mikerejsa@gmail.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).