Mail Archives: djgpp/1997/03/21/12:20:12
From: | Andy Eskilsson <x-aes AT telelogic DOT se>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Size of executable in memory?
|
Date: | 21 Mar 1997 17:02:07 +0100
|
Organization: | Telelogic AB, Sweden
|
Lines: | 27
|
Sender: | x-aes AT vega
|
Message-ID: | <ksrah9w7wg.fsf@telelogic.se>
|
Reply-To: | x-aes AT telelogic DOT se
|
NNTP-Posting-Host: | vega.telelogic.se
|
Mime-Version: | 1.0 (generated by tm-edit 7.101)
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
How memory much does the executable take?? Uh fuzzy question :-)
When making an application (python) statically, the size of the
executable is about 1 megabyte, but when stripping it the size shrinks
to 499k.
The question is now, how much extra space in memory does a 1-meg
'unstripped' executable take, compared to the same executable,
stripped to 499k?
Exactly what is it strip removes (well I don't have -g enabled and -O2
as optimization, so it shouldn't be debug-info..) and (probably the
real question is:) does this take extra memory?
If it isn't used soo much, it might not matter if it can be swapped
out, but life isn't always so simple or?
Some background:
I am messing around with DLM and python, managed to compile it, and
get it up running, but the binary is 606k, and I also need to load
DLMS (object-code?) in the size of 147+300k.. well this sums up to a
megabyte.. Can't strip it, and I wonder if it is worth these 500k's
having dynamic loading?
/Andy
- Raw text -