search for: _some_important_constants

...the section will be at > runtime, as the linker can, and will, move things around. Hmm, yes that does sound quite tricky. How do we currently deal with that for other pc-relative loads. Say the programmer writes something like this _foo: ldr r1, [pc, #392] _bar: .space 200 _baz: .space 200 _some_important_constants: .word 0x12345678 If bar and baz get deleted by the linker the offset would obviously be wrong. Do we do anything special for this or just rely on the programmer not to write this code? > We could, perhaps, always require an explicit directive for all constant > pools when using subsections...

On Nov 1, 2013, at 12:15 PM, David Peixotto <dpeixott at codeaurora.org> wrote: >>>>> I was thinking that without the .ltorg directive the constant pool >>>>> would go at the end of the section. >>>>> >>>> So where does the assembler place the constant pool(s) if that >>>> directive isn't present? I was under the