From WikiChip
Editing arm/armv8
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
This page supports semantic in-text annotations (e.g. "[[Is specified as::World Heritage Site]]") to build structured and queryable content provided by Semantic MediaWiki. For a comprehensive description on how to use annotations or the #ask parser function, please have a look at the getting started, in-text annotation, or inline queries help pages.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
{{arm title|ARMv8}}{{arm isa main}} | {{arm title|ARMv8}}{{arm isa main}} | ||
− | '''ARMv8''' | + | '''ARMv8''' is the successor to {{\\|ARMv7}}, an [[ARM]] [[instruction set architecture]] announced in [[2011]] which brought a large number of fundumental changes to the instruction set, including the introduction of 64-bit operating capabilities. |
== Overview == | == Overview == | ||
Work on the ARMv8 started within the R&D group at [[ARM Holding|ARM]] in 2007. First disclosed in late 2011, the ARMv8 is a successor and an extension to the {{\\|ARMv7}} ISA. This architecture introduced new 64-bit operating capabilities, called ''{{arm|AArch64}}'', and defined a relationship to the prior 32-bit operating state, referred to as ''{{arm|AArch32}}'' (covering the {{arm|A32}} and {{arm|T32}} ISAs). Foundationally, ARMv8 extends the old architecture while maintaining compatibility with older revisions and extensions (e.g., {{arm|Thumb}}, {{arm|NEON}}, {{arm|VFP}}) when in AArch32. Additionally, ARMv8 introduced a number of enhancements to AArch32 which still maintains full compatibility with {{\\|ARMv7}}. Generally speaking, ARMv8 was designed such that a well-designed AArch64 [[phsyical core|core]] should also work well as an AArch32 core. | Work on the ARMv8 started within the R&D group at [[ARM Holding|ARM]] in 2007. First disclosed in late 2011, the ARMv8 is a successor and an extension to the {{\\|ARMv7}} ISA. This architecture introduced new 64-bit operating capabilities, called ''{{arm|AArch64}}'', and defined a relationship to the prior 32-bit operating state, referred to as ''{{arm|AArch32}}'' (covering the {{arm|A32}} and {{arm|T32}} ISAs). Foundationally, ARMv8 extends the old architecture while maintaining compatibility with older revisions and extensions (e.g., {{arm|Thumb}}, {{arm|NEON}}, {{arm|VFP}}) when in AArch32. Additionally, ARMv8 introduced a number of enhancements to AArch32 which still maintains full compatibility with {{\\|ARMv7}}. Generally speaking, ARMv8 was designed such that a well-designed AArch64 [[phsyical core|core]] should also work well as an AArch32 core. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
=== AArch64 === | === AArch64 === | ||
{{main|arm/aarch64|l1=AArch64}} | {{main|arm/aarch64|l1=AArch64}} | ||
− | ARMv8 introduced the new {{\\|AArch64}} execution state that operates on a new instruction set called the {{\\|A64}}. This mode reworked the exception handling model in ARM, making it simpler with fewer modes and banked registers. With 64-bit support, up to 48 bits of virtual address was introduced (note that it's actually an extension of the {{arm|LPAE|Large Physical Address Extension}} which was introduced in {{\\|ARMv7}} but was developed concurrently with the ARMv8). Additionally, both security ({{arm|TrustZone}}) and virtualization carries over to AArch64. | + | ARMv8 introduced the new {{\\|AArch64}} execution state that operates on a new instruction set called the {{\\|A64}}. This mode reworked the exception handling model in ARM, making it simpler with fewer modes and banked registers. With 64-bit support, up to 48 bits of virtual address was introduced (note that it's actually an extension of the {{arm|LPAE|Large Physical Address Extension}} which was introduced in {{\\|ARMv7}} but was developed concurrently with the ARMv8). Additionally, both security ({{arm|TrustZone}}) and virtualization carries over to AArch64. |
− | |||
− | |||
− | |||
− | |||
− | |||
== Profiles == | == Profiles == | ||
Line 33: | Line 21: | ||
|- | |- | ||
| Microcontroller || ARMv8-M || Optimized for embedded systems with a highly deterministic operation. | | Microcontroller || ARMv8-M || Optimized for embedded systems with a highly deterministic operation. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
Line 91: | Line 29: | ||
* Richard Grisenthwaite. (October 26, 2011). ''"Technology Preview: The ARM Architecture - a View of the Future "''. | * Richard Grisenthwaite. (October 26, 2011). ''"Technology Preview: The ARM Architecture - a View of the Future "''. | ||
* ARM Architecture Group. "Armv8 instruction set overview." vol. PRD03-GENC-010197 (2011). | * ARM Architecture Group. "Armv8 instruction set overview." vol. PRD03-GENC-010197 (2011). | ||
− | |||
− | |||
− |