summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRyan S. Arnold <ryan.arnold@linaro.org>2017-02-14 23:02:25 +0000
committerRyan S. Arnold <ryan.arnold@linaro.org>2017-02-14 23:02:25 +0000
commit2bc6d6f21b7fbea27abc1640d06772f6283bf3d3 (patch)
tree6bcf57f1cddca7ab84859ef0c29571d7b325676a
parent796f6cfc4b6950b86e956b59b63ff0d2d3e56d80 (diff)
Added NEWS items for releases/linaro-6.3-2017.02-rc2.
-rw-r--r--components/toolchain/binaries/README.textile.series3
1 files changed, 1 insertions, 2 deletions
diff --git a/components/toolchain/binaries/README.textile.series b/components/toolchain/binaries/README.textile.series
index 627663e..8ed7ecd 100644
--- a/components/toolchain/binaries/README.textile.series
+++ b/components/toolchain/binaries/README.textile.series
@@ -75,7 +75,7 @@ Linaro GDB 7.12 (gdb-7.12-branch)
{% block news %}
{% 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 issue only affected arm targets, not AArch64. This regression has been fixed upstream and backported into Linaro GCC 6.3-2017.02-rc2.
+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 issue only affected 32-bit arm targets. This regression has been fixed upstream and backported into Linaro GCC 6.3-2017.02-rc2.
{% endcall %}
{% call format("newscont") -%}
@@ -122,7 +122,6 @@ Users of Linaro's toolchain have encountered problems when building projects wit
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 %}
-
{% call format("news") %}
The Linaro GCC 6.3-2017.01 snapshot added further enablement for ARMv8-M and these have been incorporated into this release.
{% endcall %}