Change list, documentation, and version bump for release.

CHANGES.md

@@ -1,3 +1,21 @@
+# Release 1.0.6 (2022-09-06)
+
+This release stabilizes support for macOS M1 (AArch64). Terra now
+passes 100% of the test suite on this hardware.
+
+## Changed behaviors
+
+  * Terra previously allowed `terralib.atomicrmw("xchg", ...)` to be
+    used with pointers. This was a mistake; LLVM does not allow this
+    and LLVM IR with this instruction is invalid. Terra now correctly
+    issues a type error in this situation.
+
+## Improvements
+
+  * Fixes for macOS on M1 hardware, allowing Terra to pass 100% of the
+    test suite.
+  * Automated testing is now performed regularly on PPC64le hardware.
+
 # Release 1.0.5 (2022-08-16)
 
 This release stabilizes support for ARM (AArch64). On a variety of

default.nix

@@ -43,7 +43,7 @@ let
 
 in stdenv.mkDerivation rec {
   pname = "terra";
-  version = "1.0.5";
+  version = "1.0.6";
 
   src = ./.;
 

docs/getting-started.md

@@ -19,7 +19,7 @@ The fastest way to try Terra is via [Replit](https://replit.com/@terralang/terra
 Installing Terra
 ----------------
 
-Terra currently runs on Linux (x86_64, AArch64, PPC64le), macOS (x86_64), FreeBSD (x86_64), and Windows (x86_64). Binary releases for popular versions of these systems are available [online](https://github.com/terralang/terra/releases), and we recommend you use them if possible because building Terra requires a working install of LLVM and Clang, which can be difficult to accomplish. The binaries do not require any dependencies for most operations. For interaction with the C ecosystem, such as including C header files or creating executable and shared libraries, you need to have the right development tools installed. On macOS, you need the Xcode (either Command Line Tools or a full installation); on Linux you need either the GCC or Clang toolchains (e.g., `build-essential` package in Ubuntu); and for Windows you need a copy of Microsoft Visual Studio (2015, 2017, 2019 or 2022) installed.
+Terra currently runs on Linux (x86_64, AArch64, PPC64le), macOS (x86_64, AArch64), FreeBSD (x86_64), and Windows (x86_64). Binary releases for popular versions of these systems are available [online](https://github.com/terralang/terra/releases), and we recommend you use them if possible because building Terra requires a working install of LLVM and Clang, which can be difficult to accomplish. The binaries do not require any dependencies for most operations. For interaction with the C ecosystem, such as including C header files or creating executable and shared libraries, you need to have the right development tools installed. On macOS, you need the Xcode (either Command Line Tools or a full installation); on Linux you need either the GCC or Clang toolchains (e.g., `build-essential` package in Ubuntu); and for Windows you need a copy of Microsoft Visual Studio (2015, 2017, 2019 or 2022) installed.
 
 Note that as of macOS 10.15 Catalina, in order to include C headers in Terra you will need to define the following evironment variable:
 

release/share/terra/README.md

@@ -25,7 +25,7 @@ The fastest way to try Terra is via [Replit](https://replit.com/@terralang/terra
 Installing Terra
 ================
 
-Terra currently runs on Linux (x86_64, AArch64, PPC64le), macOS (x86_64), FreeBSD (x86_64), and Windows (x86_64). Binary releases for popular versions of these systems are available [online](https://github.com/terralang/terra/releases), and we recommend you use them if possible because building Terra requires a working install of LLVM and Clang, which can be difficult to get working.
+Terra currently runs on Linux (x86_64, AArch64, PPC64le), macOS (x86_64, AArch64), FreeBSD (x86_64), and Windows (x86_64). Binary releases for popular versions of these systems are available [online](https://github.com/terralang/terra/releases), and we recommend you use them if possible because building Terra requires a working install of LLVM and Clang, which can be difficult to get working.
 
 Note that as of macOS 10.15 Catalina, in order to include C headers in Terra you will need to define the following evironment variable: