On Thu, Jul 21, 2016 at 1:53 AM, Richard Earnshaw <richard.earns...@arm.com> wrote: > On 20/07/16 22:33, Jim Wilson wrote: >> On Wed, Jul 20, 2016 at 2:14 PM, Jeffrey Walton <noloa...@gmail.com> wrote: >>> I'm having trouble with ARMv8/Aarch64. One is an early Mustang server >> >> ARMv8 implies 32-bit code (aarch32). Aaarch64 implies 64-bit code. >> These are two different compilers, with two different sets of command >> line options. > > Er, no. ARMv8 (pedantically ARMv8-A, since there are also ARMv8-R and > ARMv8-M specifications as well) is an architecture, not an ISA.
I think you are confusing the issue. We are talking about gcc here, not ARM documentation. In gcc, arm* means 32-bit code. An armv8-linux-gnu compiler is a 32-bit compiler. If I run uname -a, and see armv8a, I have a 32-bit user space. Etc. The original poster is well aware that ARMv8 is an architecture, with 32-bit and 64-bti execution modes. What he wasn't aware of was that the arm and aarch64 compilers are separate, and that if someone mentions an armv8 compiler on a gcc mailing list, then they are talking about the 32-bit arm* compiler, not the 64-bit aarch64 compiler. I did mention that both the arm and aarch64 compilers can emit ARMv8 architecture code. Jim _______________________________________________ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
