_GLOBAL_$F$
Nik Ilijic
niki@pacomsystems.com
Thu Oct 18 23:02:00 GMT 2001
I've recently started experimenting with GCC & associated tools with the
intent of replacing our existing SDS development system.
I'm working with gcc ver 2.95.3 on a linux box, compiling to an embedded
68360 target (m68k-coff target). So far I have managed to compile & link my
project, but have come across a problem with the size of the binary.
the entire code (.text) and .data sections are about twice the size as I get
with the SDS toolset. After examining the map file produced by the linker,
the biggest blowout seems to be in the data section and it is caused by
these _GLOBAL_$F$ references (see section of map file below).
What are these _GLOBAL_$F$'s and how do I get rid of them to reduce my
code/data size so that it fits into the rom & ram.
Thanks in advance,
Nik Ilijic
Development Engineer
Pacom Systems Pty. Ltd.
Australia
-------------------------------
.data 0x00c2c61c 0x1c14 port/applic/aip/aip.obj
0x00c2c658 snmpIfList
0x00c2c628 aipPtrs
0x00c2e098 AipDlink::_GLOBAL_$F$(void)
0x00c2d4f0 AipSess::_GLOBAL_$F$(short,
unsigned char *, unsigned char)
0x00c2c688 snmpIfNumber
0x00c2c68c _GLOBAL_$F$aipPtrs
.data 0x00c2e230 0xd88 port/applic/aip/snmp/snmp.obj
0x00c2ee26 mib_entries
0x00c2ee64
Aip::_GLOBAL_$F$Sif_match(SNB_ENTRY *,...)
0x00c2ee2a tabtab
0x00c2ee42 _GLOBAL_$F$mib
0x00c2e8e0 mib
0x00c2e23c Aip::_GLOBAL_$F$SnInit(void)
0x00c2e678 _GLOBAL_$F$mib_prefix
0x00c2e830 Aip::_GLOBAL_$F$GetMib(O_ID *)
0x00c2e673 mib_prefix
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
More information about the crossgcc
mailing list