![]() | This article is rated C-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||||||
|
I am not sure if the full v8a instruction set was implemented or just address space was extended to to 2TB(64bit)?
And need to add some product implementations ie. SSD/hdd models.
--:
GSMC(Chief Mike) Kouklis U.S.NAVY Ret. ⛮🇺🇸 / 🇵🇭🌴
⍨talk
09:21, 10 May 2021 (UTC)
@ Comp.arch: "conda-forge.org: "ARMv8 64-bit (formally known as `aarch64`)", just their terminology, or official?"
Presumably the intent was to ask that question here; edit comments unrelated to the edit are not the right way to ask questions about the article. Please ask them on the talk page, instead.
AArch64 is an official Arm term. As of 2022-01-10, the current edition of Arm® Architecture Reference Manual Armv8, for A-profile architecture says:
So:
We have the Arm Architecture, or the Arm CPU architecture.
It has multiple versions, including versions 7, 8, and 9.
Some of those versions have one or more profiles - the A-Profile, the R-Profile, and the M-Profile.
ARMv1 through ARMv5 have no profiles or execution states. According to the ARM Architecture Reference Manual ARMv7-A and ARMv7-R edition, ARMv4 had only the ARM instruction set, ARMv4T added Thumb, ARMv5T was the first v5 and included Thumb, ARMv6 included Thumb, and ARMv6T2 added Thumb-2.
ARMv7 introduced the profiles; an ARMv6-M profile, with Thumb only, was introduced either at that time or afterwards, but they didn't split the existing ARMv6 into ARMv6-A and ARMv6-R, as far as I can tell. ARMv7 was still 32-bit-only, with no execution states. ARMv7-A and ARMv7-R have both ARM and Thumb (including Thumb-2). ARM-v7M is Thumb-only (including Thumb-2).
Armv8 also has the profiles. It calls the ARM instruction set A32, the Thumb/Thumb-2 instruction set T32, and the new 64-bit instruction set A64. [ Armv8-A introduced the execution states; I'm not sure whether a 32-bit-only or 64-bit-only implementation is allowed. Armv8-R also has AArch32 and AArch64. ARMv8-M supports only T32.
I presume this whole mess is due to 1) trying to support everything from the microcontroller market to the server and supercomputer markets, 2) allowing that broad customer base a choice of options for their application, and 3) the instruction set now having this all designed in from Day One so it has to get added on.
AArch64 is probably what "ARMv8 64-bit" could be called, although it's not unique to ARMv8 any more, as per the Arm® Architecture Reference Manual Supplement Armv9, for Armv9-A architecture profile, Issue A.a. As far as I can tell, "ARMv8 64-bit" is not an official Arm term (if nothing else, if it were, it'd be "Armv8 64bit" :-)). Guy Harris ( talk) 02:49, 11 January 2022 (UTC)
![]() | This article is rated C-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||||||||
|
I am not sure if the full v8a instruction set was implemented or just address space was extended to to 2TB(64bit)?
And need to add some product implementations ie. SSD/hdd models.
--:
GSMC(Chief Mike) Kouklis U.S.NAVY Ret. ⛮🇺🇸 / 🇵🇭🌴
⍨talk
09:21, 10 May 2021 (UTC)
@ Comp.arch: "conda-forge.org: "ARMv8 64-bit (formally known as `aarch64`)", just their terminology, or official?"
Presumably the intent was to ask that question here; edit comments unrelated to the edit are not the right way to ask questions about the article. Please ask them on the talk page, instead.
AArch64 is an official Arm term. As of 2022-01-10, the current edition of Arm® Architecture Reference Manual Armv8, for A-profile architecture says:
So:
We have the Arm Architecture, or the Arm CPU architecture.
It has multiple versions, including versions 7, 8, and 9.
Some of those versions have one or more profiles - the A-Profile, the R-Profile, and the M-Profile.
ARMv1 through ARMv5 have no profiles or execution states. According to the ARM Architecture Reference Manual ARMv7-A and ARMv7-R edition, ARMv4 had only the ARM instruction set, ARMv4T added Thumb, ARMv5T was the first v5 and included Thumb, ARMv6 included Thumb, and ARMv6T2 added Thumb-2.
ARMv7 introduced the profiles; an ARMv6-M profile, with Thumb only, was introduced either at that time or afterwards, but they didn't split the existing ARMv6 into ARMv6-A and ARMv6-R, as far as I can tell. ARMv7 was still 32-bit-only, with no execution states. ARMv7-A and ARMv7-R have both ARM and Thumb (including Thumb-2). ARM-v7M is Thumb-only (including Thumb-2).
Armv8 also has the profiles. It calls the ARM instruction set A32, the Thumb/Thumb-2 instruction set T32, and the new 64-bit instruction set A64. [ Armv8-A introduced the execution states; I'm not sure whether a 32-bit-only or 64-bit-only implementation is allowed. Armv8-R also has AArch32 and AArch64. ARMv8-M supports only T32.
I presume this whole mess is due to 1) trying to support everything from the microcontroller market to the server and supercomputer markets, 2) allowing that broad customer base a choice of options for their application, and 3) the instruction set now having this all designed in from Day One so it has to get added on.
AArch64 is probably what "ARMv8 64-bit" could be called, although it's not unique to ARMv8 any more, as per the Arm® Architecture Reference Manual Supplement Armv9, for Armv9-A architecture profile, Issue A.a. As far as I can tell, "ARMv8 64-bit" is not an official Arm term (if nothing else, if it were, it'd be "Armv8 64bit" :-)). Guy Harris ( talk) 02:49, 11 January 2022 (UTC)