Description

GNU 10.2 cross-toolchain for the A-profile processors

Features

• Based on GCC 10.2 (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 9.2-2019.12

• Added support for Arm Neoverse V1.
• Fixed issue where the compiler was generating a conditional branch in Thumb2, which was too far for b{cond} to handle.
• Fixed issue where assembling code containing the UDF instruction results in "unknown mnemonic error" when targeting the AArch64 platform.
• Fixed issue https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96191, where the -fstack-protector option was leaving the canary value in a temporary register on return from the function.

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 requirements

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.2-2020.11-x86_64-aarch64-none-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.2-2020.11-x86_64-aarch64-none-linux-gnu.tar.xz.asc 
gcc-arm-10.2-2020.11-x86_64-aarch64-none-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 

How to build the toolchain from sources

You can build GNU cross-toolchain for the A-profile from sources using Linaro ABE (Advanced Build Environment) and provided ABE manifest files.

Below example shows how to build gcc-arm-aarch64-linux-gnu toolchain from sources using Linaro ABE build system.

Instructions

ABE has a dependency on git-new-workdir and needs this tool to be installed in /usr/local/bin directory:

$ wget https://raw.githubusercontent.com/git/git/master/contrib/workdir/git-new-workdir

$ sudo mv git-new-workdir /usr/local/bin

$ sudo chmod +x /usr/local/bin/git-new-workdir

Clone ABE from the URL below and checkout the stable branch (see Getting ABE):

$ git clone https://git.linaro.org/toolchain/abe.git

Create the build directory and change to it. Any name for the directory will work:

$ mkdir build && cd build

Configure ABE (from the build directory):

$ ../abe/configure

Download the toolchain manifest file from the GNU Arm toolchain page on developer.arm.com, for example: gcc-arm-aarch64-none-elf-abe-manifest.txt.

Build toolchain (from the build directory):

$ ../abe/abe.sh --manifest gcc-arm-aarch64-none-elf-abe-manifest.txt --build all

The built toolchain will be installed and available for use in the builds/destdir/x86_64-unknown-linux-gnu/bin/ directory.

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.

Report bugs

Please report any bugs via the Linaro Bugzilla.