This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

RE: Size of arm code

To: 'Richard Slaughter' <rslaughter at anatel dot com>, "'crossgcc at sourceware dot cygnus dot com'" <crossgcc at sourceware dot cygnus dot com>
Subject: RE: Size of arm code
From: Yves Rutschle <y dot rutschle at indigovision dot com>
Date: Tue, 13 Mar 2001 15:10:20 -0000
Encoding: 17 TEXT

> I'm building embedded applications for the ATMEL ARM EB40 
> demo board using the cygwin environment.  Using a null main 
> function and a simple CRT0.s and loader script  the smallest 
> executable I can get is about 120,000 bytes.  This is with 
> debugging and optimization off.  Does newlib  take this amout 
> of default space?  

No way; last time I heard of that on the list, it was down to
a bad linker script: different parts of the executable were
linked at different addresses, and the output was a format
not supporting segments, so the image would include large amounts
of useless padding space.

Try using objdump -h and check the size/offsets for unused areas.

Cheers,
Y.

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]