This is the mail archive of the crossgcc@sourceware.cygnus.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more infromation.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
> I'm trying to compitle a rommable image for the aeb1C. The aeb1c has a > bootloader that requires each rommable program to have a module header - > which I have placed in a file called module.c. This module header is > simply a struct containing static information about the location of the > code, name of module, etc. & is not referenced anywhere else in the > program. The problem is that this variable disappears when the program > is compiled. Maybe it gets eliminated because it's never referenced? I > don't think I have any optimizations turned on - will arm-elf-gcc simply > do this on it's own? Is there a way to turn it off? [Stephane Dalton] Probably the variable didn't disapear but if it must be at the beginning of you rommable image, you'll have to create a section which is the first one referenced by your linker script, you'll have to use the __attribute__ with the section parameter, for the linker script you can refer to ld manual and for the __attribute__ the textinfo on gcc is quite well written. Hope it will help a bit! ------ 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] |