Merge pull request #205 from theotherjimmy/add-armc6

Add ARMC6 where appropriate

Author: Amanda Butler

docs/refs/porting/mbed_targets.md

@@ -150,7 +150,7 @@ Mbed, libraries and application source code can then select different implementa
 
 ##### `supported_toolchains`
 
-The `supported_toolchains` property is the list of toolchains that support a target. The allowed values for `supported_toolchains` are `ARM`, `uARM`, `GCC_ARM` and `IAR`.
+The `supported_toolchains` property is the list of toolchains that support a target. The allowed values for `supported_toolchains` are `ARM`, `uARM`, `ARMC6`, `GCC_ARM` and `IAR`.
 
 ##### `default_toolchain`
 

docs/tutorials/first_app/blinky_cli.md

@@ -78,7 +78,7 @@ Blinky is now under `dev_directory` > `mbed-os-example-blinky`. You can look at
 Invoke `mbed compile`, specifying:
 
 * Your board: `-m <board_name>`.
-* Your toolchain: `-t <GCC_ARM`, `ARM` or `IAR`>`.
+* Your toolchain: `-t <GCC_ARM`, `ARM`, `ARMC6` or `IAR`>`.
 
 For example, for the board K64F and the Arm Compiler 5:
 

docs/tutorials/optimize/memory/memap.md

@@ -21,7 +21,7 @@ optional arguments:
   -h, --help            show this help message and exit
   -t TOOLCHAIN, --toolchain TOOLCHAIN
                         select a toolchain used to build the memory map file
-                        (ARM, GCC_ARM, IAR)
+                        (ARM, ARMC6, GCC_ARM, IAR)
   -o OUTPUT, --output OUTPUT
                         output file name
   -e EXPORT, --export EXPORT
@@ -72,7 +72,7 @@ There are other entries that require a bit of clarification:
 
 #### Current support
 
-We have tested *memap* on Windows 7, Linux and Mac OS X. The `GCC_ARM` (GNU Arm Embedded Toolchain), Arm (Arm Compiler 5) and IAR toolchains generate memory map files.
+We have tested *memap* on Windows 7, Linux and Mac OS X. The `GCC_ARM` (GNU Arm Embedded Toolchain), Arm Compiler 5, Arm Compiler 6 and IAR toolchains generate memory map files.
 
 #### Known issues and new features