search for: __at_

Hello All, In ARM embedded applications, there are some compilers that support useful function and variable attributes that help the compiler communicate information about symbols to downstream object consumers (i.e. linkers). One such attribute is the "location" attribute. This attribute can be applied to a global or local static data object or a function to indicate to the linker

...com/help/topic/com.arm.doc.dui0472m/chr1359124981140.html). In that case it was __attribute__((at(address))) but the name is not that important. The communication with the linker in that case was via section name and not symbol, from memory at(<address>) translated to a section name of .ARM.__at_<address>. For us this had some advantages: - We could use __attribute__((section(".ARM.__at_<address>"))) when the compiler didn't support the attribute, it also needed no support in the assembler. This wasn't ideal as it is nice to be able to use expressions for the...

...rm.doc.dui0472m/chr1359124981140.html). In that case it was __attribute__((at(address))) but the name is not that important. The communication with the linker in that case was via section name and not symbol, from memory at(<address>) translated to a section name of .ARM.__at_<address>. For us this had some advantages: - We could use __attribute__((section(".ARM.__at_<address>"))) when the compiler didn't support the attribute, it also needed no support in the assembler. This wasn't ideal as it is nice to be able to use expr...

...hat case it was __attribute__((at(address))) but the name is not > > that important. > > > > The communication with the linker in that case was via section name > > and not symbol, from memory at(<address>) translated to a section name > > of .ARM.__at_<address>. For us this had some advantages: > > - We could use __attribute__((section(".ARM.__at_<address>"))) when > > the compiler didn't support the attribute, it also needed no support > > in the assembler. This wasn't ideal as it is n...

...hat case it was __attribute__((at(address))) but the name is not > > that important. > > > > The communication with the linker in that case was via section name > > and not symbol, from memory at(<address>) translated to a section name > > of .ARM.__at_<address>. For us this had some advantages: > > - We could use __attribute__((section(".ARM.__at_<address>"))) when > > the compiler didn't support the attribute, it also needed no support > > in the assembler. This wasn't ideal as it is n...

...t >> > > that important. >> > > >> > > The communication with the linker in that case was via section >> name >> > > and not symbol, from memory at(<address>) translated to a section >> name >> > > of .ARM.__at_<address>. For us this had some advantages: >> > > - We could use __attribute__((section(".ARM.__at_<address>"))) >> when >> > > the compiler didn't support the attribute, it also needed no >> support >> > > in the...

...ddress))) but the name is > not > > > that important. > > > > > > The communication with the linker in that case was via section name > > > and not symbol, from memory at(<address>) translated to a section > name > > > of .ARM.__at_<address>. For us this had some advantages: > > > - We could use __attribute__((section(".ARM.__at_<address>"))) > when > > > the compiler didn't support the attribute, it also needed no > support > > > in the assembler. This was...