|
Hi all, I am using vdsp2.0 and SHARC-21060 processor for my codec project. I have been using .map file generated to determine the memory requirements for the code. Is that approach correct. It gives something called "memory word used" and "memory words unused". But I am getting confused about the .dxe file size that is generated.It is quite huge and confusing the .map file results. Is there any other method to determine the exact size of the code/data like .ldr file or any other format. It will be nice if u can share some documents on this. I am greedy to know in this regard from u all. thanks and regards Hemant |
|
|
map file
Started by ●September 23, 2003
Reply by ●September 23, 20032003-09-23
|
On Tue, 23 Sep 2003, hemant ramdasi wrote: > I am using vdsp2.0 and SHARC-21060 processor for my > codec project. > I have been using .map file generated to determine the > memory requirements for the code. > Is that approach correct. It gives something called > "memory word used" and "memory words unused". In your achetecture file you specify memory size, so "unused" refers to zones the linker didn't need but are specified. > But I am getting confused about the .dxe file size > that is generated.It is quite huge and confusing the > .map file results. Did you compile with -g (debugger) info? Then you have a lot of excess data (pointers and addresses and etc...) > Is there any other method to determine the exact size > of the code/data like .ldr file or any other format. Look at the commands for the linker and see what option you need to create "executable only". That will eliminate all the source and cross reference info and should match the map file (other than header info for each segment). Patience, persistence, truth, Dr. mike |
|
|
Reply by ●September 23, 20032003-09-23
|
--On Tuesday, September 23, 2003 6:31 AM -0700 Mike Rosing <> wrote: > Did you compile with -g (debugger) info? Then you have a lot > of excess data (pointers and addresses and etc...) Debug information is kept in separate non-loadable sections. The only effect of enabling debugging is that it disables some optimizations and makes the code a bit bigger. Instead of the map file, you could also run elfdump against the dxe to see the size of its sections. List the section headers for that. |
