[meta-xilinx] U-Boot compilation problems using external toolchain

[David Holsgrove]

Hi Martin,

I believe the root cause of this issue is mostly likely a bug we had discovered with the lshrsi3_with_size_opt insn pattern in gcc for microblaze - present in the toolchain shipped in XSDK 2013.3.

This bug was triggered as you have seen by optimizing for size.

It has been fixed, and will be available in the toolchains which will ship with Xilinx's upcoming 2013.4 release.

Alternatively, it is also fixed in the toolchain which has already shipped in the new PetaLinux SDK v2013.10 release.

thanks,
David

> -----Original Message-----
> From: meta-xilinx-bounces at yoctoproject.org [mailto:meta-xilinx-
> bounces at yoctoproject.org] On Behalf Of Martin Townsend
> Sent: Wednesday, 11 December 2013 10:28 PM
> To: meta-xilinx at yoctoproject.org
> Subject: [meta-xilinx] U-Boot compilation problems using external toolchain
>
> Hi,
>
> The current toolchain that comes with SDK 2013.3 builds a U-Boot image
> that always fails to pass the CRC when loading the environment from
> flash.  After taking out the checks the environment is loaded and there
> is nothing wrong with it but U-Boot still fails to read certain
> variables out of the environment.  After hacking the U-Boot config.mk
> file to replace the -Os with -O2 everything works as expected so I
> assume there is a problem with the compiler optimising for speed.
>
> My question is what external toolchain should I by using? I tried the
> toolchain that gets built within the latest Poky distribution but this
> had similar problems with other packages.
>
> Cheers,
> Martin.
> _______________________________________________
> meta-xilinx mailing list
> meta-xilinx at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-xilinx



This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.