Description

GNU 10.3 cross-toolchain for the A-profile processors

Features

• Based on GCC 10.3 (See https://gcc.gnu.org/gcc-10/changes.html for details).
• Supported targets on Windows(x86_64): AArch64 (bare-metal and Linux), AArch32 (bare-metal, Linux hard-float)
• Supported targets on Linux(x86_64): AArch64 (bare-metal, Linux, Linux big-endian), AArch32 (bare-metal, Linux hard-float)
• Supported targets on Linux(AArch64): AArch64 (bare-metal), AArch32 (bare-metal, Linux hard-float)

Changes since Arm release GCC 10.2-2020.11

• Bumped binutils to version 2.36.1.
• Bumped glibc to version 2.33.
• Bumped newlib to a version from May 2021.

• Fixed the security vulnerability described in https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3420.

• The toolchain executables for Windows host are signed with SHA2.

• Fixed issue https://sourceware.org/bugzilla/show_bug.cgi?id=25235 where forward-referencing ADR instructions were generating wrong offsets in Thumb code.

• Fixed issue https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95253 where the toolchain on Windows host generated incorrect paths in the output dependency file.

• Fixed issue https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97236 where wrong code might be generated for Aarch64 targets when using -O3 optimization.

• Fixed an issue where files opened in binary mode on AArch64 might be incorrectly handled.

Content

This release includes the following items:

Known dependencies

GDB's Python support requires Python compiled with UCS-4 support (built with --enable-unicode=ucs4) for Linux (x86_64) and Windows hosts

GDB's Python support requires Python DLL dependencies for Windows host.

Toolchains dedicated for Windows host require mingw-w64 library, a complete runtime environment for GCC.

The following executables in the Windows hosted toolchains:

• aarch64-none-linux-gnu-dwp.exe

• aarch64-none-linux-gnu-ld.gold.exe

• arm-none-linux-gnueabihf-dwp

• arm-none-linux-gnueabihf-ld.gold.exe

have additional dependencies on the following dlls:

• libwinpthread-1.dll
• libgcc_s_sjlj-1.dll
• libstdc++-6.dll
• libgcc_s_dw2-1.dll

You can obtain the required dlls from the MinGW-W64 GCC-8.1.0 packages from SourceForge:

• i686-posix-sjlj
• i686-posix-dwarf

The GNU Toolchains

The package names of the released GNU toolchain binaries have the following naming convention:

gcc-arm-<Release Version>-<Host>-<Target Triple>.tar.xz

Host

Released files

Installation instructions

Extract XZ compressed release archive using TAR archiving utility:

   $ tar -xJf <toolchain binary> -C <destination directory>

Example for Linux(x86_64) hosted for AArch64 Linux target

   $ tar -xJf gcc-arm-10.3-2021.07-x86_64-aarch64-linux-gnu.tar.xz -C /path/to/destination/directory

Compute and check MD5 checksum of XZ compressed release archives using md5sum utility:

   $ md5sum --check gcc-arm-10.3-2021.07-x86_64-aarch64-linux-gnu.tar.xz.asc 

   gcc-arm-10.3-2021.07-x86_64-aarch64-linux-gnu.tar.xz: OK

The prebuilt binary bundles can be un-tarred and executed in place.  Unpack the Linux cross toolchain:

   $ mkdir install-lnx
   $ tar x -C install-lnx -f <filename>.tar.xz
   $ PATH=`pwd`/install-lnx/<filename>/bin:$PATH 

Known issues

• When you decompress the windows packages, the decompression requests permission to overwrite certain files. This is because the files have similar names with different case, which are treated as identical names on a Windows host. You can choose to overwrite the files with identical names.

• When using the toolchains dedicated for the Windows host, if you invoke the compiler from the installed toolchain's bin directory and you use the -flto option without using the -c option, then the linker generates this error message:
  error: lto-wrapper failed
  collect2.exe: error: ld returned 1 exit status
  To avoid this error message, you must invoke the compiler from any directory other than the installed toolchain's bin directory.

Ask questions

For any questions, please use the Arm Communities forums (https://community.arm.com/developer/tools-software/tools)

Report bugs

Please report any bugs via the Linaro Bugzilla (https://bugs.linaro.org/)