From: "C Jaiprakash, Noida" <cjaiprakash@hcltech.com>
To: binutils@sources.redhat.com
Cc: "C Jaiprakash, Noida" <cjaiprakash@hcltech.com>
Subject: File size increases significantly after objcopy
Date: Thu, 25 Nov 2004 13:22:00 -0000 [thread overview]
Message-ID: <267988DEACEC5A4D86D5FCD780313FBB020AB76F@exch-03.noida.hcltech.com> (raw)
Hi,
I am building colilo for a coldfire (v4e) target. I am facing a strange
problem. If i build colilo with -O0 option and convert the ELF binary to
bnary, srec format following are the resulting file sizes
-rwxr-xr-x 1 cjaiprakash coldfire 93K Nov 25 18:58 colilo.bin
-rwxr-xr-x 1 cjaiprakash coldfire 123K Nov 25 18:58 colilo.elf
-rw-r--r-- 1 cjaiprakash coldfire 279K Nov 25 18:58 colilo.s19
-rw-r--r-- 1 cjaiprakash coldfire 279K Nov 25 18:58 colilo.srec
But when i build the colilo with -O2 option file size increase
significantly, following are the sizes
-rwxr-xr-x 1 cjaiprakash coldfire 17M Nov 25 19:01 colilo.bin
-rwxr-xr-x 1 cjaiprakash coldfire 107K Nov 25 19:01 colilo.elf
-rw-r--r-- 1 cjaiprakash coldfire 49M Nov 25 19:01 colilo.s19
-rw-r--r-- 1 cjaiprakash coldfire 49M Nov 25 19:01 colilo.srec
ELF binary size is ok but why the file sizes for bin, srec are so huge?
Thanks and best regards,
C Jaiprakash
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Contributing to the World by creating indispensable value !
System Software CoE @ HCLT-Noida
http://www.hcltechnologies.com
Ph. : +91-120-2510701/702 Ext : 3170
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
next reply other threads:[~2004-11-25 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 13:22 C Jaiprakash, Noida [this message]
2004-11-25 14:05 ` Andreas Schwab
2004-11-25 15:53 ` Peter Barada
2004-11-25 15:56 ` Peter Barada
2004-11-25 13:23 C Jaiprakash, Noida
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=267988DEACEC5A4D86D5FCD780313FBB020AB76F@exch-03.noida.hcltech.com \
--to=cjaiprakash@hcltech.com \
--cc=binutils@sources.redhat.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).