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]
Other format: [Raw text]

Generate "custom" bss section that doen't occupy space in ELF


I generated a custom bss section:


volatile Byte Fieldbuffer[Fieldbuffersize] __attribute__ ((aligned(4)))
__attribute__ ((section(".bss_uc")));


And in the linker script:

  /* uncached bss section */
  .bss_uc (NOLOAD) :
  {
    *(.bss_uc .bss_uc.*)
  } >dram_uc

The gernerated datastructures in bss_uc should not be statically initialized
at any place.

But I get a very big ELF file (luckily not the HEX file out of objcopy),
which contains data for this 'bss_uc' section.

(NOLOAD) didn't help.

How could I get my bss_uc the same way as the predefined bss so that it's
data is not placed in the ELF ?

Raymund Hofmann


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


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