Update naming to `aarch32` and `aarch64`.

Change-Id: I40a929b1095ee3e1b2ca5ef879c7006d8b59acc9

7 files changed, 20 insertions, 19 deletions

diff --git a/doc/design/a32/literal-pool.md b/doc/design/aarch32/literal-pool.md
index 6adef20b..95cc76de 100644
--- a/doc/design/a32/literal-pool.md
+++ b/doc/design/aarch32/literal-pool.md
@@ -96,7 +96,7 @@ assembler)... So, it’s pretty hard to manage all this. Here's a gdb trace:
         vixl::aarch64::Assembler::LinkAndGetWordOffsetTo (this=0x7fffffffd550, literal)
         637   literal->SetLastUse(GetCursorOffset());
 
-          vixl::aarch64::RawLiteral::SetLastUse (this, offset=40) at src/vixl/a64/assembler-a64.h:1151
+          vixl::aarch64::RawLiteral::SetLastUse (this, offset=40) at src/vixl/aarch64/assembler-aarch64.h:1151
           1154        offset_ = -offset - 1;
 
         vixl::aarch64::Assembler::LinkAndGetWordOffsetTo (this, literal)
@@ -108,10 +108,10 @@ assembler)... So, it’s pretty hard to manage all this. Here's a gdb trace:
             vixl::aarch64::LiteralPool::UpdateFirstUse(this, use_position=40)
             140     SetNextRecommendedCheckpoint(NextRecommendedCheckpoint());
 
-              vixl::aarch64::LiteralPool::NextRecommendedCheckpoint (this) at src/vixl/a64/macro-assembler-a64.h:155
+              vixl::aarch64::LiteralPool::NextRecommendedCheckpoint (this) at src/vixl/aarch64/macro-assembler-aarch64.h:155
               155   return first_use_ + kRecommendedLiteralPoolRange;
 
-            vixl::aarch64::LiteralPool::SetNextRecommendedCheckpoint (this, offset=131112) at src/vixl/a64/macro-assembler-a64.h:3130
+            vixl::aarch64::LiteralPool::SetNextRecommendedCheckpoint (this, offset=131112) at src/vixl/aarch64/macro-assembler-aarch64.h:3130
             3129      masm_->recommended_checkpoint_ =
             3130          std::min(masm_->recommended_checkpoint_, offset);
 ** Note that we've modified a *private* member of the MacroAssembler through a call to the assembler **
diff --git a/doc/getting-started-a32.md b/doc/getting-started-aarch32.md
index 7e8e785c..0a4e5da8 100644
--- a/doc/getting-started-a32.md
+++ b/doc/getting-started-aarch32.md
@@ -8,7 +8,7 @@ details on a few useful features provided by VIXL and see how to run the
 generated code.
 
 The source code of the example developed in this guide can be found in the
-`examples/a32` directory (`examples/a32/getting-started.cc`).
+`examples/aarch32` directory (`examples/aarch32/getting-started.cc`).
 
 
 Creating the macro assembler.
@@ -21,9 +21,9 @@ file:
     #include <stdio.h>
     #include <string>
     #include <stdint.h>
-    #include "a32/constants-a32.h"
-    #include "a32/instructions-a32.h"
-    #include "a32/macro-assembler-a32.h"
+    #include "aarch32/constants-aarch32.h"
+    #include "aarch32/instructions-aarch32.h"
+    #include "aarch32/macro-assembler-aarch32.h"
 
 In our case, those files are included by "examples.h".
 
@@ -184,7 +184,7 @@ A little trace:
 
 The example shown in this tutorial is very simple, because the goal was to
 demonstrate the basics of the VIXL framework. There are more complex code
-examples in the VIXL `examples/a32` directory showing more features of both the
+examples in the VIXL `examples/aarch32` directory showing more features of both the
 macro assembler and the AArch32 architecture.
 
 Disassembling the generated code.
@@ -199,7 +199,7 @@ First, you must include iostream.
 
 And the disassembler header file:
 
-    #include "a32/disasm-a32.h"
+    #include "aarch32/disasm-aarch32.h"
 
 Then you have to define the pc used to disassemble (the one which is used to
 display the addresses not the location of the instructions):
diff --git a/doc/getting-started-a64.md b/doc/getting-started-aarch64.md
index 7e04116b..5c3958c0 100644
--- a/doc/getting-started-a64.md
+++ b/doc/getting-started-aarch64.md
@@ -8,7 +8,7 @@ details on a few useful features provided by VIXL and see how to run the
 generated code in the VIXL simulator.
 
 The source code of the example developed in this guide can be found in the
-`examples/a64` directory (`examples/a64/getting-started.cc`).
+`examples/aarch64` directory (`examples/aarch64/getting-started.cc`).
 
 
 Creating the macro assembler and the simulator.
@@ -18,8 +18,8 @@ First of all you need to make sure that the header files for the assembler and
 the simulator are included. You should have the following lines at the beginning
 of your source file:
 
-    #include "a64/simulator-a64.h"
-    #include "a64/macro-assembler-a64.h"
+    #include "aarch64/simulator-aarch64.h"
+    #include "aarch64/macro-assembler-aarch64.h"
 
 VIXL's assembler will generate some code at run-time, and this code needs to
 be stored in a buffer. It must be large enough to contain all of the
@@ -202,5 +202,5 @@ the value of the registers after the execution. For instance:
 
 The example shown in this tutorial is very simple, because the goal was to
 demonstrate the basics of the VIXL framework. There are more complex code
-examples in the VIXL `examples/a64` directory showing more features of both the
+examples in the VIXL `examples/aarch64` directory showing more features of both the
 macro assembler and the ARMv8 architecture.
diff --git a/doc/supported-instructions-a64.md b/doc/supported-instructions-aarch64.md
index b9d2e626..b9d2e626 100644
--- a/doc/supported-instructions-a64.md
+++ b/doc/supported-instructions-aarch64.md
diff --git a/doc/topics/a64/extending-the-disassembler.md b/doc/topics/aarch64/extending-the-disassembler.md
index fe9da196..60b04b3f 100644
--- a/doc/topics/a64/extending-the-disassembler.md
+++ b/doc/topics/aarch64/extending-the-disassembler.md
@@ -10,8 +10,8 @@ The general procedure to achieve this is to create a sub-class of
 
 The `Disassembler` class provides virtual methods that implement how specific
 disassembly elements are printed. See
-[src/a64/disasm-a64.h](/src/a64/disasm-a64.h) for details. These include
-functions like:
+[src/aarch64/disasm-aarch64.h](/src/aarch64/disasm-aarch64.h) for details.
+These include functions like:
 
     virtual void AppendRegisterNameToOutput(const Instruction* instr,
                                             const CPURegister& reg);
@@ -30,7 +30,7 @@ of the disassembler. The VIXL `Decoder` uses a visitor pattern implementation,
 so the `Disassembler` (as a sub-class of `DecoderVisitor`) must provide a
 visitor function for each sub-type of instructions. The complete list of
 visitors is defined by the macro `VISITOR_LIST` in
-[src/a64/decoder-a64.h](/src/a64/decoder-a64.h).
+[src/aarch64/decoder-aarch64.h](/src/aarch64/decoder-aarch64.h).
 
 The [/examples/custom-disassembler.h](/examples/custom-disassembler.h) and
 [/examples/custom-disassembler.cc](/examples/custom-disassembler.cc) example
@@ -54,6 +54,7 @@ map code addresses, annotate code addresses, and add comments:
 
 
 One can refer to the implementation of visitor functions for the `Disassembler`
-(in [src/a64/disasm-a64.cc](/src/a64/disasm-a64.cc)) or even for the `Simulator`
-(in [src/a64/simulator-a64.cc](/src/a64/simulator-a64.cc)) to see how to extract
-information from instructions.
+(in [src/aarch64/disasm-aarch64.cc](/src/aarch64/disasm-aarch64.cc)) or even
+for the `Simulator`
+(in [src/aarch64/simulator-aarch64.cc](/src/aarch64/simulator-aarch64.cc))
+to see how to extract information from instructions.
diff --git a/doc/topics/a64/index.md b/doc/topics/aarch64/index.md
index e38aaad3..e38aaad3 100644
--- a/doc/topics/a64/index.md
+++ b/doc/topics/aarch64/index.md
diff --git a/doc/topics/a64/ycm.md b/doc/topics/aarch64/ycm.md
index 36371cf3..36371cf3 100644
--- a/doc/topics/a64/ycm.md
+++ b/doc/topics/aarch64/ycm.md