On 9/12/19 1:48 AM, Jonas Pfeil wrote:
> Yes, you are correct. Tested it and it works as intended.
>
> Thanks,
>
> Jonas
>
> --- a/gcc/config/microblaze/microblaze.h
> +++ b/gcc/config/microblaze/microblaze.h
> @@ -695,7 +695,7 @@ do {
>
"\t.ascii\t"
#define STRING_ASM_OP "\t.asciz\t"
-Ursprüngliche Nachricht-
Von: Jeff Law
Gesendet: Mittwoch, 11. September 2019 19:33
An: Jonas Pfeil ; gcc-patches@gcc.gnu.org
Betreff: Re: Fix for type confusion bug on microblaze
On 9/11/19 5:28 AM, Jonas Pfei
On 9/11/19 5:28 AM, Jonas Pfeil wrote:
> The Microblaze target confuses unsigned long with HOST_WIDE_INT.
>
> This works fine for many architectures, but fails on ARM (HOST_WIDE_INT is 8
> bytes, unsigned long is 4 bytes). Leading to print a uninitialized register
> instead of the desired number,
The Microblaze target confuses unsigned long with HOST_WIDE_INT.
This works fine for many architectures, but fails on ARM (HOST_WIDE_INT is 8
bytes, unsigned long is 4 bytes). Leading to print a uninitialized register
instead of the desired number, fix by using the correct printf-specifier.
Teste
