From: Sam Lantinga <slouken@devolution.com>
To: Joe Buck <jbuck@Synopsys.COM>
Cc: slouken@devolution.com, egcs@egcs.cygnus.com, highlander@lokigames.com
Subject: Re: Large code size?
Date: Wed, 24 Mar 1999 16:28:00 -0000 [thread overview]
Message-ID: <E10Py0p-0001gL-00@roboto.devolution.com> (raw)
> > We built robotcom.so with the compiler flags:
> > g++ -O2 -funroll-loops -fno-exceptions -DLINUX_BETA -D_REENTRANT
> > and the linker flags:
> > cc -shared -nostartfiles -s -o robotcom.so ...
> Hmm. Does the gnu.linkonce trick work for shared libraries?
> (If you were building an executable and multiple .o files use,
> say, vector<int>, more than one .o file would have a definition
> of some of the vector<int> functions but the GNU linker would
> eliminate all but one copy. I don't think this works for shared
> libraries, though I may be wrong).
The code size increase happens with both the binary and the shared library.
The shared library is just much smaller, so I was more easily able to tweak
the compilation flags.
The final link is done, and the result with the above flags on the main
binary gives:
-rwxrwxr-x 1 hercules devel 8299204 Mar 25 08:13 civctp
[hercules@asgard src]$ size civctp
text data bss dec hex filename
5455970 2786012 1327492 9569474 9204c2 civctp
That's a whopping 4.5MB decrease in size just by using -fno-exceptions
It's still 25% larger than the equivalent VC++ code (which does have
exception handling enabled, BTW), but .5 MB of that is additional library
code that is a separate DLL on Windows, for a final count of only 17%
larger.
Thanks!
-Sam Lantinga (slouken@devolution.com)
Lead Programmer, Loki Entertainment Software
--
Author of Simple DirectMedia Layer -
http://www.devolution.com/~slouken/SDL/
--
WARNING: multiple messages have this Message-ID
From: Sam Lantinga <slouken@devolution.com>
To: Joe Buck <jbuck@Synopsys.COM>
Cc: slouken@devolution.com, egcs@egcs.cygnus.com, highlander@lokigames.com
Subject: Re: Large code size?
Date: Wed, 31 Mar 1999 23:46:00 -0000 [thread overview]
Message-ID: <E10Py0p-0001gL-00@roboto.devolution.com> (raw)
Message-ID: <19990331234600.9rVKyv8_4ysgNSCmOc9vFVT6JOXc7KmGLUAxbO3mWXc@z> (raw)
> > We built robotcom.so with the compiler flags:
> > g++ -O2 -funroll-loops -fno-exceptions -DLINUX_BETA -D_REENTRANT
> > and the linker flags:
> > cc -shared -nostartfiles -s -o robotcom.so ...
> Hmm. Does the gnu.linkonce trick work for shared libraries?
> (If you were building an executable and multiple .o files use,
> say, vector<int>, more than one .o file would have a definition
> of some of the vector<int> functions but the GNU linker would
> eliminate all but one copy. I don't think this works for shared
> libraries, though I may be wrong).
The code size increase happens with both the binary and the shared library.
The shared library is just much smaller, so I was more easily able to tweak
the compilation flags.
The final link is done, and the result with the above flags on the main
binary gives:
-rwxrwxr-x 1 hercules devel 8299204 Mar 25 08:13 civctp
[hercules@asgard src]$ size civctp
text data bss dec hex filename
5455970 2786012 1327492 9569474 9204c2 civctp
That's a whopping 4.5MB decrease in size just by using -fno-exceptions
It's still 25% larger than the equivalent VC++ code (which does have
exception handling enabled, BTW), but .5 MB of that is additional library
code that is a separate DLL on Windows, for a final count of only 17%
larger.
Thanks!
-Sam Lantinga (slouken@devolution.com)
Lead Programmer, Loki Entertainment Software
--
Author of Simple DirectMedia Layer -
http://www.devolution.com/~slouken/SDL/
--
next reply other threads:[~1999-03-24 16:28 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-24 16:28 Sam Lantinga [this message]
[not found] ` < E10Py0p-0001gL-00@roboto.devolution.com >
1999-03-24 16:45 ` Joe Buck
1999-03-31 23:46 ` Joe Buck
1999-03-31 23:46 ` Sam Lantinga
-- strict thread matches above, loose matches on Subject: below --
1999-03-25 9:49 Sam Lantinga
[not found] ` < E10QEFo-0002NA-00@roboto.devolution.com >
1999-03-25 10:14 ` H.J. Lu
1999-03-31 23:46 ` H.J. Lu
1999-03-31 23:46 ` Sam Lantinga
1999-03-25 9:48 Sam Lantinga
1999-03-25 11:24 ` Jason Merrill
1999-03-31 23:46 ` Jason Merrill
1999-03-31 23:46 ` Sam Lantinga
1999-03-24 17:57 N8TM
1999-03-31 23:46 ` N8TM
1999-03-24 16:47 Sam Lantinga
1999-03-31 23:46 ` Sam Lantinga
1999-03-24 16:34 Mike Stump
1999-03-31 23:46 ` Mike Stump
1999-03-24 15:42 Sam Lantinga
[not found] ` < E10PxHr-0001fO-00@roboto.devolution.com >
1999-03-24 15:54 ` Joe Buck
[not found] ` < 199903242353.PAA02719@atrus.synopsys.com >
1999-03-24 23:22 ` Martin v. Loewis
1999-03-31 23:46 ` Martin v. Loewis
1999-03-31 23:46 ` Joe Buck
1999-03-24 17:07 ` H.J. Lu
[not found] ` < m10PycJ-000ErMC@ocean.lucon.org >
1999-03-25 5:04 ` Nick Ing-Simmons
1999-03-31 23:46 ` Nick Ing-Simmons
1999-03-31 23:46 ` H.J. Lu
[not found] ` <199903242353.PAA02719.cygnus.egcs@atrus.synopsys.com>
1999-03-25 1:08 ` Jason Merrill
1999-03-25 8:28 ` Andi Kleen
1999-03-31 23:46 ` Andi Kleen
[not found] ` < u9n212vswe.fsf@yorick.cygnus.com >
1999-03-25 14:35 ` Martin v. Loewis
1999-03-31 23:46 ` Martin v. Loewis
1999-03-31 23:46 ` Jason Merrill
1999-03-31 23:46 ` Sam Lantinga
1999-03-24 15:05 Sam Lantinga
[not found] ` < E10PwfK-0001bs-00@roboto.devolution.com >
1999-03-24 23:26 ` Martin v. Loewis
1999-03-31 23:46 ` Martin v. Loewis
1999-03-24 23:35 ` Martin v. Loewis
1999-03-31 23:46 ` Martin v. Loewis
1999-03-31 23:46 ` Sam Lantinga
[not found] <E10PwA2-0001UN-00@roboto.devolution.com>
1999-03-24 14:42 ` Martin von Loewis
1999-03-24 14:49 ` Dima Volodin
1999-03-31 23:46 ` Dima Volodin
1999-03-31 23:46 ` Martin von Loewis
1999-03-24 13:52 Sam Lantinga
[not found] ` < E10PvY5-0001NJ-00@roboto.devolution.com >
1999-03-24 14:10 ` Martin v. Loewis
1999-03-31 23:46 ` Martin v. Loewis
1999-03-24 15:18 ` H.J. Lu
1999-03-31 23:46 ` H.J. Lu
1999-03-31 23:46 ` Sam Lantinga
1999-03-24 9:38 Sam Lantinga
[not found] ` < E10PrbT-0003Og-00@roboto.devolution.com >
1999-03-24 13:29 ` David B. Rees
1999-03-31 23:46 ` David B. Rees
1999-03-24 13:38 ` Martin v. Loewis
1999-03-31 23:46 ` Martin v. Loewis
1999-03-31 23:46 ` Sam Lantinga
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=E10Py0p-0001gL-00@roboto.devolution.com \
--to=slouken@devolution.com \
--cc=egcs@egcs.cygnus.com \
--cc=highlander@lokigames.com \
--cc=jbuck@Synopsys.COM \
/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).