Added NEWS items for releases/linaro-6.3-2017.02-rc2.

1 files changed, 4 insertions, 3 deletions

diff --git a/components/toolchain/binaries/README.textile.series b/components/toolchain/binaries/README.textile.series
index 2db798d..90c071b 100644
--- a/components/toolchain/binaries/README.textile.series
+++ b/components/toolchain/binaries/README.textile.series
@@ -75,14 +75,15 @@ Linaro GDB 7.12 (gdb-7.12-branch)
 {% call format("news") -%}
 A bug/regression in the compiler has been identified whereby the target function that is invoked when calling a "weak" function directly is the "strong" override, whereas when calling the function via a pointer the "weak" implementation is used.  This would be noticed as inconsisent function invocation when invoking directly vs. invoking via function pointer.  This regression has been fixed upstream and backported into Linaro GCC 6.3-2017.02-rc2.
 {% endcall %}
+
 {% call format("newscont") -%}
-GCC PR target/78253: [5/6/7 Regression] [ARM] call weak function instead of strong when called through pointer
+GCC PR target/78253: [5/6/7 Regression] [ARM] call weak function instead of strong when called through pointer.
 {% endcall %}
 
 {{ urlind(6,"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78253") }}
 
 {% call format("news") -%}
-MS Windows does not support symlinks and extractors do not always handle them correctly (by copying) when unpacking archives that contain them.  The Linaro binary toolchain MS Windows extractor did not properly copy the symlinks target files/directories into the necessary directory structure when unpacking the toolchain archive which caused problems with missing dependencies for the following users of the Linaro mingw toolchains:
+MS Windows does not support symlinks and the MS Windows archive extractor does not properly deep copy the symlink target files/directories into the symlinked directory structure when unpacking the toolchain archive.  This causes problems with missing dependencies when using the Linaro mingw toolchains, as identified in the following bugs:
 {% endcall %}
 
 {{ urlind(6,"https://bugs.linaro.org/show_bug.cgi?id=2684") }}
@@ -116,7 +117,7 @@ Users of Linaro's toolchain have encountered problems when building projects wit
 {{ urlind(6,"https://bugs.linaro.org/show_bug.cgi?id=2764") }}
 
 {% call format("newscont") %}
-The Linaro binary toolchain releases contain *.la files, which are artifacts of the toolchain build process.  These .la files are helper files for libtool, but unlike a gcc install tree, they are not position independent and contain full paths.  Since these artifacts contain absolute paths they can actually 'mislead' user invocation of libtool into not finding required libraries (because they reference the build tree, not the install location) and hence breaking Autotools builds.  These *.la file artifacts have been removed from Linaro toolchain binaries because they are unnecessary for users.
+The Linaro binary toolchain release contained files with a .la suffix as artifacts of the toolchain build process.  These .la files are helper files for libtool, but unlike a gcc install tree, they are not position independent and contain full paths.  Since these artifacts contain absolute paths they can actually mislead user invocation of libtool into not finding required libraries (because they reference the build tree, not the install location) and hence breaking Autotools builds.  These *.la file artifacts have been removed from Linaro toolchain binaries because they are unnecessary for users.
 {% endcall %}