Hi Frederic,
Frederic Beaulieu wrote:
Hi guys,
I try to understand the executable "msp430-size"
provide with the mspgcc package and I have few
questions about it:
1- Why it is only text, data and bss sections which
are analyzed and not custom sections added manually in
the linker script?
It's the nature of the program to use one of two output formats giving
the size of the three standard segments (that are common for all
architectures and configurations): text, data and bss;
You can get additional information about the sizes of the other (custom)
segments or the real (! as rick already wrote: with "size" not reliable
in any case) sizes of the standard segments using the nm tool (refer to
mail fom ).
2- Why, in some case, msp430-size don't return output
in dec and hex fields? I have seen also some .elf
where msp430-size don't return output for all fields
(text, data, bss, dec and hex)!
I'm interested in these cases, never heared about this. Could you mail
some examples with the corresponding command line options?
3- What dec and hex outputs really represents?
The sum of text + data + bss sizes in decimal and hexadecimal
representation.
N.B. I use it on windows XP
If this makes anything better ;-) (just kidding).
Best regards
Arnd-Hendrik
Thanks a lot in advance for your answers!!!
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
