In message <[EMAIL PROTECTED]> you wrote:
>
> > Maybe just adding some ".align" directive helps?
>
> The example provided for 8xx or others, there is an offset alignment
> after CONFIG_IDENT_STRING - ". =3D EXC_OFF_SYS_RESET". In fact, it works
> after adding ".align 4" after CONFIG_IDENT_STRING.
Wolfgang,
> Maybe just adding some ".align" directive helps?
The example provided for 8xx or others, there is an offset alignment
after CONFIG_IDENT_STRING - ". = EXC_OFF_SYS_RESET". In fact, it works
after adding ".align 4" after CONFIG_IDENT_STRING.
Thanks.
Regards,
TsiChung
In message <[EMAIL PROTECTED]> you wrote:
>
> > This is intentional on most architectures. What exactly is your
> > problem?
>
> Apparently, it is not the case in ColdFire compilers. The ColdFire
> compilers always put the version_string in text section if .data is not
> declared and shows build
Wolfgang,
In message
<[EMAIL PROTECTED]> you
wrote:
>> The compiler does not place the .ascii in start.S to data section,
>> instead it put in under text section. This is an issue where it
> This is intentional on most architectures. What exactly is your
> problem?
Apparently, it is not the ca
In message <[EMAIL PROTECTED]> you wrote:
> The compiler does not place the .ascii in start.S to data section,
> instead it put in under text section. This is an issue where it
This is intentional on most architectures. What exactly is your
problem?
> never gets notice and causes error until an u
The compiler does not place the .ascii in start.S to data section,
instead it put in under text section. This is an issue where it
never gets notice and causes error until an update for
tools/setlocalversion has been applied. A label of .data before
.globl version_string will force to put under dat
