The answer is no.

The tool chain you are referencing is old, and works for 32bit architectures.

You need this (ubuntu): sudo apt-get install gcc-aarch64-linux-gnu g++-aarch64-linux-gnu

ILP32 and ILP64 are both AArch64, just one of them is limited to 32-bit addresses, but instruction encoding is the same. For that you will need to use a special toolchain. I have not tried this, but you should Google for "AArch64 ILP32 toolchain". Looks like it's not actively maintained though. If you want AArch32, that is just ARMv7 and you need the regular arm toolchain (arm-linux-gnueabihf). https://wiki.linaro.org/Platform/arm64-ilp32

(I have the same confusion. And I try to answer it based on my investigation/understanding.)

Possible Naming Schema

According to quote from ARM GNU Toolchain Downloads page, bare metal and Linux are two different targets. And to differentiate from the target architecture, I call it target environment. And my way to tell it is: if it has "linux" in the name, it targets Linux environment, otherwise bare metal.

Available for bare-metal and Linux targets

So I interpret the toolchain names with below schema:

...<host_arch>-<target_arch>-<vendor>-<target_env+abi>

1. Host OS: on what OS the toolchain itself runs. This is not part of the name but listed in the toolchain download page.

2. Host Arch: on what machine architecture the toolchain itself runs.

3. Target Arch: What machine architecture the toolchain's output targets.

4. Vendor: Who offers the toolchain.

5. Target Environment: can be bare metal or GNU/Linux.

6. ABI: things like call conventions for assembly functions. This is related to both architecture and OS (link). So far I have seen: eabi/elf/linux-gnu/linux-gnueabi

About the "target_env+abi" part

I think this is the most confusing part. ABI is related to machine architecture, OS and language (link). And I think below naming convention holds based on the both the Target Arch + Target Environment.

1. For AArch32 + bare metal, use "eabi".

2. For AArch64 + bare metal, use "elf". (similar to eabi)

3. For AArch32 + Linux/GNU, use "linux-gnueabi" (eabi generated by gcc)

4. For AArch64 + Linux/GNU, use "linux-gnu" (maybe similar to 3 just like 2 to 1)

So I think all 4 of them are about EABI. But may have some subtle differences.

Hope some guru can shed some light here.

Examples

Let's take some toolchain names from the ARM GNU Toolchain Downloads page as examples.

Example 1:
arm-gnu-toolchain-14.2.rel1-mingw-w64-i686-arm-none-eabi.zip

1. Host Arch = x86-64 because of the "mingw-w64-i686"

2. Host OS = Windows because listed so.

3. Target Arch = AArch32 because of the arm.

4. Target Environment = bare metal because no linux in the name.

5. Vendor: by open-source community, no specific vendor so it is none.

6. ABI = eabi

Example 2:
arm-gnu-toolchain-14.2.rel1-mingw-w64-i686-arm-none-linux-gnueabihf.zip

1. Host Arch = x86-64 because of the "mingw-w64-i686"

2. Host OS = Windows because listed so.

3. Target Arch = AArch32 because of the arm.

4. Target Environment = GNU Linux because of the "linux" in the name.

5. Vendor: by open-source community, no specific vendor so it is none.

6. ABI = linux-gnueabi

Example 3:
arm-gnu-toolchain-14.2.rel1-mingw-w64-i686-aarch64-none-elf.zip

1. Host Arch = x86-64 because of the "mingw-w64-i686"

2. Host OS = Windows because listed so.

3. Target Arch = AArch64 because of the "aarch64".

4. Target Environment = bare metal because no linux in the name.

5. Vendor: by open-source community, no specific vendor so it is none.

6. ABI = elf

Example 4:
arm-gnu-toolchain-14.2.rel1-x86_64-arm-none-eabi.tar.xz

1. Host Arch = x86-64 because of the "x86_64"

2. Host OS = Linux because listed so.

3. Target Arch = AArch32 because of the "arm".

4. Target Environment = bare metal because no linux in the name.

5. Vendor: by open-source community, no specific vendor so it is none.

6. ABI = eabi

Example 5:
arm-gnu-toolchain-14.2.rel1-aarch64-aarch64-none-linux-gnu.tar.xz

1. Host Arch = AArch64 because of the first "aarch64"

2. Host OS = Linux because listed in Linux-hosted section

3. Target Arch = AArch64 because of the second "aarch64".

4. Target Environment = GNU Linux because of the "linux" in the name.

5. Vendor: by open-source community, no specific vendor so it is none.

6. ABI = linux-gnu

To answer the original question

• aarch64-none-elf: is for AArch64 bare metal, vendor is none

• arm-none-eabi: is for AArch32 bare metal, vendor is none