ColdFire: Fix alignment issue after CONFIG_IDENT_STRING in start.S
When the version_string function in start.S is not 4-byte align, it will cause the compiler generates "unaligned opcodes detected in executable segment". This issue affects all ColdFire CPUs. By adding .align 4 after CONFIG_IDENT_STRING, it will pad 0's if it is not aligned. Signed-off-by:TsiChung Liew <Tsi-Chung.Liew@freescale.com> Acked-by:
John Rigby <jrigby@freescale.com>
Showing
- cpu/mcf5227x/start.S 1 addition, 0 deletionscpu/mcf5227x/start.S
- cpu/mcf523x/start.S 1 addition, 0 deletionscpu/mcf523x/start.S
- cpu/mcf52x2/start.S 1 addition, 0 deletionscpu/mcf52x2/start.S
- cpu/mcf532x/start.S 1 addition, 0 deletionscpu/mcf532x/start.S
- cpu/mcf5445x/start.S 1 addition, 0 deletionscpu/mcf5445x/start.S
- cpu/mcf547x_8x/start.S 1 addition, 0 deletionscpu/mcf547x_8x/start.S
Loading
Please register or sign in to comment