Passing by address results in compiler miscalculation?

When I use a local struct variable of type RCC_ClocksTypeDef (part of the ST peripheral library) and I call the RCC_GetClocksFreq() function passing the local struct as the parameter, for some reason...
Passing by address results in compiler miscalculation?

When I use a local struct variable of type RCC_ClocksTypeDef (part of the ST peripheral library) and I call the RCC_GetClocksFreq() function passing the local struct as the parameter, for some reason...
Using __attribute__((at(address)))

Hi, I hope someone can shed a light on this, I have a board with a LCP2294 and 4Mb IDT71V416L external RAM. Using Keil RealView 3.01 I used the "__at 0x81000000" modifier to place a global...
Using __attribute__((at(address)))

Hi, I hope someone can shed a light on this, I have a board with a LCP2294 and 4Mb IDT71V416L external RAM. Using Keil RealView 3.01 I used the "__at 0x81000000" modifier to place a global...
Compiler assumes array addresses are aligned for structs declared with __attribute__((packed))

If I have a struct declared like the following: volatile struct { uint8_t foo; int16_t bar[1]; } __attribute__((packed)) foobar; The code emitted uses LDRSH to access bar[0] and causes a hardfault...