A static global is no problem.  BUT if I remove the "static"
declaration, arm-elf-ld puts the global along with other non-static
globals in a section starting at memory address 0.

You can imagine that this is a Very Bad Thing.

The behavior occurs with a linker command file that looks like the
following.  Interestingly, if the IROM_or_IRAM memory region is omitted
from the command file, the non-static globals are put someplace sane.
But the command file never mentions that anything should be put in
IROM_or_IRAM -- so why does the presence of that informational line
alter how the loader behaves?

I'm aware there are other ways to write a linker command file, but is
this approach wrong?  Why should static or non-static make a difference
to the linker?  Isn't a .bss a .bss?  Well, I'll just remove the
informational IROM_or_IRAM line, it doesn't need to be there anyway.

Thanks for any insights!  --Bill


******** arm-elf-ld command file ********
ENTRY(main)

MEMORY
{
        IROM_or_IRAM (RWX): ORIGIN = 0, LENGTH = 64K /* On-chip */
        IRAM (RWX): ORIGIN = 0x08000000, LENGTH = 64K /* Direct access
*/
}

SECTIONS
{
        .bundle :
        {
                *(.vectors)
                *(.text)
                *(.rodata*)
                *(.glue*)
                _end_rodata = .;
                *(.data)
                *(.bss)
        } > IRAM
}

******** sample code ********
volatile int aGlobal;

int main ()
{
  aGlobal = 1;
  return (aGlobal);
}

******** arm-elf-nm output of the above ********
0800002c T _end_rodata
00000000 B aGlobal <----- HELP!
08000000 T main

******** arm-elf-nm output if "static" inserted before "volatile int"
********
0800002c T _end_rodata
0800002c t aGlobal  <----- THAT'S MORE LIKE IT
08000000 T main