Merge branch 'arc-dev' into arc-staging

Author: wangnuannuan

NEWS

@@ -1,3 +1,52 @@
+Major Changes in 2020.03 Release
+================================
+
+Toolchain and IDE Components Versions
+-------------------------------------
+
+* Binutils 2.34 with ARC patches
+* GCC 9.3 with ARC patches
+* GDB 10-prerelease with ARC patches
+* newlib 3.2.0 with ARC patches
+* uClibc-ng v1.0.31
+* glibc 2.30 with ARC patches
+* Eclipse 2018-12 4.10.0 with CDT 9.6.0
+* OpenOCD 0.9+ upstream commit 30203b3d8b, with ARC support.
+
+This release of GNU toolchain and IDE is supported by CGEN IPlib (TCF generator) version 1.0.53 and later.
+
+New Features and Enhancements
+-----------------------------
+
+* Binary distribution
+	* Supported host operating systems: Windows 10 64-bit, Ubuntu 16.04.x, 18.04.x, CentOS/RHEL 7.x
+	* No longer compatible with CentOS/RHEL 6.x due to GDB 8.3 requirement for C++11 support in the compiler.
+          Still it's perfectly possible to build Elf32 & uClibc toolchains without GDB on CentOS/RHEL 6.x.
+
+* Toolchain Build Scripts
+	* Documentation update
+
+* GCC
+	* Update to GCC 9.3, see upstream release notes for more details: https://gcc.gnu.org/pipermail/gcc/2020-March/000037.html
+	* Refurbished interrupt handling code
+	* Use of GP & FP registers as general-purpose registers
+	* Bug fixes
+
+* GDB
+	* Binutils & GDB now use the same code base. Though for simplisity & compatibility of build-system we still keep separate branches for each component.
+	* GDB code is based on what will become v10.0.
+
+* Binutils
+	* Updated to Binutils 2.34, see upstream release notes for more details: https://lists.gnu.org/archive/html/info-gnu/2020-02/msg00000.html
+	* Bug fixes
+
+* glibc
+	* No changes since 2019.09 release
+
+* Eclipse plugins
+	* Bug fixes
+
+
 Major Changes in 2019.09 Release
 ================================
 
@@ -41,6 +90,7 @@ New Features and Enhancements
 	* Updated to upstream 2.30, see upstream release notes for more details:  https://sourceware.org/ml/libc-alpha/2019-08/msg00029.html
 	* ARC patches submitted for upstream submission as of Jan 2019
 	* MMU page size gets detected automatically in run-time via getpagesize()
+	* Added hardware floating point support
 	* Enabled big-endian ARC support
 
 * Eclipse plugins

README.md

@@ -12,8 +12,6 @@ Branches in this repository are:
   candidates. Head of this branch is either a latest stable release or latest
   release candidate for the upcoming release
 * `arc-dev` is the development branch for the current toolchain release
-* `arc-4.8-dev` is the development branch for the 4.8 toolchain release
-* `arc-4.4-dev` is the development branch for the 4.4 toolchain release
 
 While the top of *development* branches should build and run reliably, there
 is no guarantee of this. Users who encountered an error are welcomed to create
@@ -28,7 +26,7 @@ components to versions corresponding to the toolchain branch. Build script from
 development branch of toolchain repository will by default check out latest
 development branches of components. Build script from release and staging
 branches will check out components to the corresponding git tag. For example
-build script for 2015.06 release will checkout out components to arc-2015.06
+build script for 2020.03 release will checkout out components to arc-2020.03-release
 tag.
 
 
@@ -237,10 +235,10 @@ If current working directory is not a "toolchain" directory, then change to it:
     $ cd toolchain
 
 This repository can be checked out to a specific GNU Toolchain for ARC release
-by specifying a particular release tag, for example for 2016.03 release that
+by specifying a particular release tag, for example for 2020.03 release that
 would be:
 
-    $ git checkout arc-2016.03
+    $ git checkout arc-2020.03-release
 
 
 Building the Toolchain
@@ -282,9 +280,9 @@ The most important options of `build-all.sh` are:
    chains. Combined with `--no-multilib` this option allows to build GNU
    toolhain that supports only one specific core. Valid values depend on what
    is available in GCC As of version 2016.03 values available in ARC GCC are:
-   em, arcem, em4, em4_dmips, em4_fpus, em4_fpuda, quarkse, hs, archs, hs34,
-   hs38, hs38_linux, arc600, arc600_norm, arc600_mul64, arc600_mul32x16,
-   arc601, arc601_norm, arc601_mul64, arc601_mul32x16, arc700. Note that only
+   `em`, `arcem`, `em4`, `em4_dmips`, `em4_fpus`, `em4_fpuda`, `quarkse`, `hs`, `archs`, `hs34`,
+   `hs38`, `hs38_linux`, `arc600`, `arc600_norm`, `arc600_mul64`, `arc600_mul32x16`,
+   `arc601`, `arc601_norm`, `arc601_mul64`, `arc601_mul32x16`, `arc700`. Note that only
    ARC 700 and ARC HS can be selected as a default core for Linux toolchain.
  * `--host <triplet>` - option to set host triplet of toolchain. That allows to
    do Canadian cross-compilation, where toolchain for ARC processors

doc/conf.py

@@ -49,17 +49,17 @@
 
 # General information about the project.
 project = 'GNU Toolchain for ARC User Manual'
-copyright = '2016-2019, Synopsys'
+copyright = '2016-2020, Synopsys'
 author = 'Synopsys'
 
 # The version info for the project you're documenting, acts as replacement for
 # |version| and |release|, also used in various other places throughout the
 # built documents.
 #
 # The short X.Y version.
-version = '2019.09'
+version = '2020.03'
 # The full version, including alpha/beta/rc tags.
-release = '2019.09'
+release = '2020.03'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.