[ACTIVITY] Sept 29 - Oct 4

[Ryan Arnold]

== Progress ==
  * Finished most new employee onboarding
  * Setup Chromebook with Linux Ubuntu (crouton) development environment.

  * glibc
[PATCH] Update generic swapon definition to match prototype.

  * CBuildV2
[PATCH] Fix stamp-configure* name for git repos with specific named branches
[PATCH] Only return early on error following configure
[PATCH] Remove dryrun wrapper from git-new-workdir invocation.
[PATCH] Fix stamp name for git repos with specific named branches.
[PATCH] Remove lynx check from configure[.ac]. It's no longer used.

Started working on a patch to fix git working directory branch
name for named branches.

== Plan ==
  * Install Fedora 19 on work laptop that just (Oct 4) arrived and
setup working environment.

  * Finish first-pass fixes on cbuildv2.

  * Complete patch to fix git working directory branch name.

  * Start working on a glibc.git conf file to potentially move away
from eglibc.git.

  * Fix cbuildv2 fetch time stamps. They seem to always be downloading
tar balls.

  * Fix stamp output so that it doesn't imply that stamps or older
than a file when stamps do not yet exist.

== Issue ==

  * Temporary desktop corruption and couldn't Linux 'rescue' from an
encrypted drive. Spent part of Tuesday rescuing my work environment
off the drive and reinstalling system.

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ACTIVITY] Week 41 : Oct 7 - Oct 11

[Ryan Arnold]

== Progress ==
* CbuildV2 Fixes to add fetch md5sums to testsuite/test.sh:

-  Subject: [PATCH][test_fetch_md5sums 1/2] lib/fetch.sh: Add
missing ${local_snapshots} to md5sum path.

- Subject: [PATCH][test_fetch_md5sums 2/2] testsuite/test.sh: Add
fetch tests section.


* CbuildV2 Fixes to get testsuite/test.sh working in the source directory:

- Subject: [PATCH][cbuild2 1/3] testsuite/test.sh: Don't use
"warning" function before it is sourced.

- Subject: [PATCH][cbuild2 2/3] testsuite/test.sh: Remove
redundant sourcing of host.conf.

- Subject: [PATCH][cbuild2 3/3] testsuite/test.sh: Re-enable
running tests from src dir.

CbuildV2 random fixes:

- Subject: [PATCH][cbuild2 2/4] cbuild2.sh: correct --disable "boostrap"

- Subject: [PATCH][cbuild2 3/4] config/ffmpeg.conf: separate options


* CbuildV2 fixes to remove ${dir}/md5sums usage (it is redunant with
snapshots/md5sums).

- Subject: [PATCH][cbuild2 1/4] Remove unneeded
infrastructure/md5sums fragment

- Subject: [PATCH][cbuild2 4/4] Remove ${dir} specific md5sums files.

* Fixed error where gcc stage 2 configure returns early (erroneously)
on success.

- [PATCH] Only return early on error following configure

* Fixed error in downloading branch named git repos in lib/checkout.sh.

- [PATCH] Fix git clone to get repo without branch name as part of the url.

== Issues ==

Contacted its@linaro requesting permission to be able to create
personal branches in rsavoye’s cbuild2 git tree.  They created a group
for cbuildv2.

Got work laptop installed (dualboot) with Fedora 19 and ran into some
errors with secure boot.

== Plan ==

* Spend some time looking at our options with regard to EGLIBC options
groups when forced to move to glibc proper.

*

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ACTIVITY] Week 40 : Oct 14 - Oct 18

[Ryan Arnold]

== Progress ==
eglibc -> glibc transition:
  * Investigated upstream plan to retire eglibc and the implication of
losing options groups.

Cbuildv2
  *


[PATCH][test_fetch_md5sums_fix] testsuite/test.sh: Always override
${local_snapshots} for tests.

[PATCH][test_fetch_md5sums_fix] testsuite/test.sh: Add second fetch
md5sums test and always use wget -q in testsuite.




== Issues ==

* None

== Plan ==

Objective before Linaro Connect:
  * Wiki/README on using cbuildv2 sources.conf and .conf:latest=
  * git workflow document: collaborative use of git in Linaro
  * wiki/README on using cbuildv2 local_snapshots for
specific/non-remote archives or git repositories.

General Cbuildv2:
  * Audit usage of "local foo=`bar`; if test $?". Change to: "local
foo; foo=`bar`; if test $?".
- This is a known issue and very nefarious.
  * Investigate dryrun to use stderr 2>&1?
  * Port get_URL, get_source, and find_snapshot to unique behind
/@ return type.
  * Test local_snapshot overrides

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ACTIVITY] Week 40 : Oct 14 - Oct 18

[Ryan Arnold]

I accidentally sent without completing my 'Progress' section.

== Progress ==
eglibc -> glibc transition:
  * Investigated upstream plan to retire eglibc and the implication of
losing options groups.

Cbuildv2 - Random patches

  * [PATCH][Cbuildv2/get_source 17/17] lib/common.sh: get_source - Fix
for partial match in snapshots with .conf:latest set.
  * [PATCH][Cbuildv2/get_source 16/17] testsuite/test.sh: Add get_URL
test for .git@revision.
  * [PATCH][Cbuildv2/get_source 15/17] lib/common.sh: Fix so that
get_URL works for .git@revision.
  * [PATCH][Cbuildv2/get_source 14/17]
testsuite:test_sources.conf|test.sh: reserve nomatch.git for testing.
  * [PATCH][Cbuildv2/get_source 13/17] testsuite/test.sh: Add tests
for user git repos not ending in .git.
  * [PATCH][Cbuildv2/get_source 12/17] [test_]sources.conf: Unify
behind .git identifiers for all git repos.
  * [PATCH][Cbuildb2/get_source 11/17] New variable ${sources_conf} to
replace hardcoded config/sources.conf.
  * [PATCH][Cbuildv2/get_source 10/17] testsuite/test.sh: Add test for
tag matching an svn repo in sources.conf.
  * [PATCH][Cbuildv2/get_source 09/17] lib/common.sh: echo ${url} in
leg that processes direct non .git repositories.
  * [PATCH][Cbuildv2/get_source 08/17] lib/common.sh: Fix for
unknown/unmatched get_source request.
  * [PATCH][Cbuildv2/get_source 07/17] lib/common.sh: echo ${url} in
get_source when finding a successful snapshot match.
  * [PATCH][Cbuildv2/get_source 06/17] lib/common.sh: find_snapshot
should return list of found snapshots even on error.
  * [PATCH][Cbuildv2/get_source 05/17] lib/common.sh: Invoke
find_snapshot as a subshell in get_source.
  * [PATCH][Cbuildv2/get_source 04/17] lib/common.sh: Suppress
extraneous trailing whitespace in get_URL and get_source output.
  * [PATCH][Cbuildv2/get_source 03/17] testsuite/test.sh: Suppress
stderr noise and add new failing get_source tests.
  * [PATCH][Cbuildv2/get_source 02/17] lib/checkout.sh: checkout
should use get_srcdir to reuse code.
  * [PATCH][Cbuilv2/get_source 01/17] lib/make.sh: Don't continue with
build if source isn't found.
  * [PATCH][Cbuildv2/get_source 00/17] Patchset to exhaustively test
get_source code legs and fix corner cases.

  * [PATCH] cbuild2/lib/common.sh: redirect trace/error/warning, etc. to stderr.

  * [PATCH] cbuild/lib/configure.sh: Fix stamp-configure* to prevent
spurious configure running.

  * [COMMITTED][PATCH] cbuild/lib/make.sh: Add ${builddir}/install.log
from make install output.

  * [COMMITTED][PATCH] lib/common.sh (list_URL): correct bash keyword
"locals" -> "local".

  * [COMMITTED][PATCH] config/gcc.conf: Add --disable-shared to stage
1 default_configure_flags.

  * [PATCH][test_fetch_md5sums_fix] testsuite/test.sh: Add second
fetch md5sums test and always use wget -q in testsuite.
  * [PATCH][test_fetch_md5sums_fix] testsuite/test.sh: Always override
${local_snapshots} for tests.

== Issues ==

* None

== Plan ==

Objective before Linaro Connect:
  * Wiki/README on using cbuildv2 sources.conf and .conf:latest=
  * git workflow document: collaborative use of git in Linaro
  * wiki/README on using cbuildv2 local_snapshots for
specific/non-remote archives or git repositories.

General Cbuildv2:
  * Audit usage of "local foo=`bar`; if test $?". Change to: "local
foo; foo=`bar`; if test $?".
- This is a known issue and very nefarious.
  * Investigate dryrun to use stderr 2>&1?
  * Port get_URL, get_source, and find_snapshot to unique behind
/@ return type.
  * Test local_snapshot overrides

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ACTIVITY] Week 43 : Oct 21 - Oct 25

[Ryan Arnold]

== Progress ==

  * [PATCH][Cbuildv2/symlinks] lib/fetch.sh: Move tar unpacking to
before symlink creation.
  * cbuild2/glibc branch - Uploaded alpha glibc support in cbuild2
(which required pretty signifcant refactoring).
  * Improving bounds checking of cbuild2 command line arguments

== Issues ==

  * None

== Plan ==
  * Harden cbuild2 command line support
  * Finish documentation/usage for cbuild2
  * Integrate glibc enablement into cbuild2 master branch

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ACTIVITY] Week 45 - Nov 4 - Nov 8

[Ryan Arnold]

== Progress ==

* Monday off for recovery from Connect.
* Created git_revisions branch for refactoring
  * Added verified and correct --help and --usage text.
  * Error check for spurios '=' after --
  * Add toplevel test.sh for testing cbuild2.sh commands
  * Fix get_URL and checkout to support git revisions.
  * Improve dryrun to prevent grepping missing files.
  * Added glibc support to cbuild2.
* Cleaned up merged cbuildv2 remote development branches
* Started cbuild2 bisect.

== Plan ==
* Merge glibc support upstream

== Issues ==

 * None

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ACTIVITY] Week 46

[Ryan Arnold]

Forgot to hit send on this one

== Progress ==

*Add documentation for git-parser.sh.

*lib/git-parser.sh: Add no-url support.

*testsuite/test.sh fix invocation of testsuite/git-parser-tests.sh
to include ${topdir}.

*Add lib/git-parser.sh and testsuite/git-parser-tests.sh.

 *  Fix corner cases with @/.git[/branch]@

1) Allow http urls to be processed by 'git' cases.

2) Error check git-new-workdir and git checkout

3) Parse revision and branch properly when there might be a @
   in the url.

*testsuite/test.sh: Update for breath to cover
user@/.git@

*Fix get_srcdir to work with @.git/branch@revision

*Fix get_toolname and get_srcdir when using @.git@revision

== Issues ==
*   None
== Next ==

 *Have cbuild2 start using the git parser

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ACTIVITY] Week 47 (short holiday week)

[Ryan Arnold]

== Progress ==
*lib/git-parser.sh: Add support for ~ as branch designator and
multi-/ branches.
*Refactor cbuild2 to use git parser
*Created stamp functions for cbuild2

US Thanksgiving Holiday

== Next ==

* Finish refactor of cbuild2 to use git parser.
* Create unified parser that wraps git parser.
* Finish refactor of cbuild2 to use stamp functions.

== Issues ==
*   None

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ACTIVITY] Week 49

[Ryan Arnold]

== Progress ==

* TCWG-367 drop --dostep, add --checkout (1/10)

Completed with following git commits:

commit 2d4d7588c1b05801ee5e1a924c8641ff7c322c07
Author: Ryan S. Arnold 
Date:   Fri Dec 6 11:46:40 2013 -0600

cbuild2.sh: remove --dostep.  It's no longer supported.

Also added testcase to make sure it returns an error.

Author: Ryan S. Arnold 
Date:   Fri Dec 6 10:57:34 2013 -0600

Add cbuild2 --checkout |all support with tests

* misc (1/10)

commit 9fb1c4404f8065ef844154e614ff4e7086fce176
Author: Ryan S. Arnold 
Date:   Thu Dec 5 12:21:20 2013 -0600

 lib/package.sh: git status should be run in the current directory.

commit 7bb4a9ce8ef440655fe45e6819b57da8d61e8728
Author: Ryan S. Arnold 
Date:   Wed Dec 4 11:47:56 2013 -0600

lib/package.sh: git st should be git status.

* TCWG-356 Unify GIT URL parsing (5/10)
* TCWG-359 Change branch character (2/10)

Closed with following git commits:

commit c9368930e6fb1ad46d08c2dbcc34d8167344ad28
Author: Ryan S. Arnold 
Date:   Tue Dec 3 16:29:00 2013 -0600

Finish git parser refactoring, use stamp functions, complete
dryrun wrapping.

commit eabbc74e48bc8c3a4addbc53ec6a492521193a0c
Author: Ryan S. Arnold 
Date:   Wed Nov 27 16:31:20 2013 -0600

Working additions for git parser refactor and stamping.

== Issues ==

*misc (1/10)
- Discovered a bug in glibc when using upstream (4.9) gcc that isn't
present in 4.8.  This might have something to do with how binutils
interacts with the compiler instead of simply a compiler issue:

elf/dl-addr.c:152: multiple definition of `_dl_addr_inside_object'
elf/dl-open.c:746: first defined here

== Plan ==

* Create card for new glibc multiple definition problem,
* Start working on glibc related cards

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

Re: [ACTIVITY] Week 49

[Ryan Arnold]

Thanks Andrew, you just saved me a bunch of tail-chasing!

Ryan

On Fri, Dec 6, 2013 at 5:31 PM, Pinski, Andrew
 wrote:
>>- Discovered a bug in glibc when using upstream (4.9) gcc that isn't present 
>>in 4.8.
>
> This is due to a bug in both glibc and gcc.  See 
> https://sourceware.org/ml/libc-alpha/2013-11/msg00291.html for some 
> information about the glibc side of things.
> http://gcc.gnu.org/ml/gcc-patches/2013-12/msg00374.html and 
> http://gcc.gnu.org/ml/gcc-patches/2013-11/msg01374.html 
> (http://gcc.gnu.org/ml/gcc-patches/2013-12/msg00283.html) for the GCC side of 
> things.
>
> Thanks,
> Andrew Pinski
>
> 
> From: linaro-toolchain-boun...@lists.linaro.org 
>  on behalf of Ryan Arnold 
> 
> Sent: Friday, December 06, 2013 3:24 PM
> To: Linaro Toolchain
> Subject: [ACTIVITY] Week 49
>
> == Progress ==
>
> * TCWG-367 drop --dostep, add --checkout (1/10)
>
> Completed with following git commits:
>
> commit 2d4d7588c1b05801ee5e1a924c8641ff7c322c07
> Author: Ryan S. Arnold 
> Date:   Fri Dec 6 11:46:40 2013 -0600
>
> cbuild2.sh: remove --dostep.  It's no longer supported.
>
> Also added testcase to make sure it returns an error.
>
> Author: Ryan S. Arnold 
> Date:   Fri Dec 6 10:57:34 2013 -0600
>
> Add cbuild2 --checkout |all support with tests
>
> * misc (1/10)
>
> commit 9fb1c4404f8065ef844154e614ff4e7086fce176
> Author: Ryan S. Arnold 
> Date:   Thu Dec 5 12:21:20 2013 -0600
>
>  lib/package.sh: git status should be run in the current directory.
>
> commit 7bb4a9ce8ef440655fe45e6819b57da8d61e8728
> Author: Ryan S. Arnold 
> Date:   Wed Dec 4 11:47:56 2013 -0600
>
> lib/package.sh: git st should be git status.
>
> * TCWG-356 Unify GIT URL parsing (5/10)
> * TCWG-359 Change branch character (2/10)
>
> Closed with following git commits:
>
> commit c9368930e6fb1ad46d08c2dbcc34d8167344ad28
> Author: Ryan S. Arnold 
> Date:   Tue Dec 3 16:29:00 2013 -0600
>
> Finish git parser refactoring, use stamp functions, complete
> dryrun wrapping.
>
> commit eabbc74e48bc8c3a4addbc53ec6a492521193a0c
> Author: Ryan S. Arnold 
> Date:   Wed Nov 27 16:31:20 2013 -0600
>
> Working additions for git parser refactor and stamping.
>
> == Issues ==
>
> *misc (1/10)
> - Discovered a bug in glibc when using upstream (4.9) gcc that isn't
> present in 4.8.  This might have something to do with how binutils
> interacts with the compiler instead of simply a compiler issue:
>
> elf/dl-addr.c:152: multiple definition of `_dl_addr_inside_object'
> elf/dl-open.c:746: first defined here
>
> == Plan ==
>
> * Create card for new glibc multiple definition problem,
> * Start working on glibc related cards
>
> ___
> linaro-toolchain mailing list
> linaro-toolchain@lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-toolchain

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ACTIVITY] Week 50 (Dec 9 - Dec 13)

[Ryan Arnold]

== Progress == (4/10)

* TCWG-372 fix Cbuildv2 parsing to handle the new binutils-gdb repository (4/10)
-  Completed Card with following commits.

commit e6e39f5d1f7963332b3d7dd2e4400de91847219c
Author: Ryan S. Arnold 
Date:   Tue Dec 10 16:08:17 2013 -0600

Correct get_toolname to work with unified repo: binutils-gdb.git

Secondary fixes required:

- Set config/binutils.conf and config/gdb.conf to use unified repo
binutils-gdb.git.

- Re-enable binutils-gdb.git in config/sources.conf.

- get_toolname now calls get_git_tool and determines the actual toolname
for binutils and gdb from the branch name if the repository is unified.

- Made all other usages of get_git_tool use get_toolname instead.

- checkout() now uses ${repo} as returned from get_git_repo as the git
repository instead of ${tool}.git.  This allows a unified repository to
only be checked out once.

- The git parser now determines whether an http:// in a url means a git
service or an svn service.

- The git parser now returns branch names for launchpad urls with branches
in the url.

- The git parser now returns the tool name properly for an svn service.

- The git parser testsuite now has testcases for all new additions.

Also

- Added --snapshots functionality to allow specifying an existing snapshots
directory.
- Add testcases to test.sh to test --snapshots functionality.
- Changes test.sh --snapshots directive to --md5sums to avoid confusion
with cbuild2.sh --snapshots.


* TCWG-323 Interface hardening (5/10)
- Card in progress with following commits:

commit cc7193d8ddb86c4ed7d16086f8ee968ae4bae87f
Author: Ryan S. Arnold 
Date:   Thu Dec 12 11:40:00 2013 -0600

cbuild2.sh: All error exit paths should use build_failure().


commit 2a4ec7fa0b7c48e0c6e05a7549f64e3336022f45
Author: Ryan S. Arnold 
Date:   Wed Dec 11 14:08:51 2013 -0600

cbuild2.sh: Added check_directive() to unify bounds checking.

Also added accompanying top-level test.sh fragments to test
check_directive.

Change-Id: Ia42a4b241a5ca62d41dccf1d8e023980ad0a04d0

commit c9ec21200260bdb26d9fe9b26d7ce390579a0ca2
Author: Ryan S. Arnold 
Date:   Wed Dec 11 13:07:15 2013 -0600

test.sh: Fixed to work with a temporary host.conf file.

Require change due to commit 3b5c576630a8ac08cd3b9ab9eab781308549a858
which requires a host.conf file for finding the cbuild topdir.

Change-Id: I991bb5f2a7949267bf69fba093d6becd202ad138

commit 16a45027be798b06160916234713f5dc35b2ecbb
Author: Ryan S. Arnold 
Date:   Tue Dec 10 18:16:09 2013 -0600

cbuild2.sh: Bounds check --set input.

Change-Id: I8ebffd1809b17962aef58f2a08277d5f639d7e3e

commit d7ee602c24231e24457c93208f749cbdd0357115
Author: Ryan S. Arnold 
Date:   Tue Dec 10 18:03:04 2013 -0600

cbuild2.sh: Remove --srcdir.  It didn't do anything.

Change-Id: I5b99c7ae8dc542cb62516104bd0bf9d1888afc52

commit 53e9c74966442c41cc9512f27f46ef849d62bcc8
Author: Ryan S. Arnold 
Date:   Tue Dec 10 17:58:54 2013 -0600

cbuild2.sh: Remove --dispatch support.  It didn't do anything.

commit 289ade38f100872653218da4792fbb1650d3b231
Author: Ryan S. Arnold 
Date:   Wed Dec 11 10:27:37 2013 -0600

cbuild2.sh: Bounds check --release switch.

Change-Id: I90804ea02b995d476b148fb68db955d164bc674c

commit 9bae259ebbff193e29899edf8a47190747d2bc1b
Author: Ryan S. Arnold 
Date:   Wed Dec 11 10:09:00 2013 -0600

lib/configure.sh: Add missing closing "

Change-Id: I9eee9a934a6cbb60bd1e2db6b0af9faf19fa5188

commit 16a45027be798b06160916234713f5dc35b2ecbb
Author: Ryan S. Arnold 
Date:   Tue Dec 10 18:16:09 2013 -0600

cbuild2.sh: Bounds check --set input.

Change-Id: I8ebffd1809b17962aef58f2a08277d5f639d7e3e

commit d7ee602c24231e24457c93208f749cbdd0357115
Author: Ryan S. Arnold 
Date:   Tue Dec 10 18:03:04 2013 -0600

cbuild2.sh: Remove --srcdir.  It didn't do anything.

Change-Id: I5b99c7ae8dc542cb62516104bd0bf9d1888afc52

commit 53e9c74966442c41cc9512f27f46ef849d62bcc8
Author: Ryan S. Arnold 
Date:   Tue Dec 10 17:58:54 2013 -0600

cbuild2.sh: Remove --dispatch support.  It didn't do anything.

Change-Id: I4b6ee8db0d3e74510b95c816469b0c100207972f

* Misc (1/10)
- Now using gerrit with git review for handling cbuildv2 development.
- Reviewed V Chong's proposed outline for toolchain documentation and
made suggestions and edits.

== Plan ==
* Move onto working primarily on glibc Jira cards.

== Issues ==
* Lab migration took cbuild.validation.linaro.org down for several
unplanned days and therefore toolchain sources were unavailable during
that time.  I made do by adding some features into cbuildv2 to use
alternative snapshots directories.

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ACTIVITY] Week 1 - Jan 6 - 10

[Ryan Arnold]

== Progress ==
* Draft wiki page (under ACL--let me know if you want to see) for
instructions for setting up chroots on chromebooks for glibc testing:

https://collaborate.linaro.org/display/~ryan.arn...@linaro.org/Configuring+a+Chromebook+for+Toolchain+Testing

* Investigated expanding remote testing possibilities in glibc.

* RFC email to libc-alpha discussing proposal for glibc host testsuite
in chroots:

https://sourceware.org/ml/libc-alpha/2014-01/msg00222.html

== Issues ==

* Shortened week (3-days) because of unplanned school closures on
Monday and Tuesday due to freezing temperatures, during which I had to
watch my kids.

== Plan ==

* Start code scaffolding for glibc host testsuite in chroot.
* Start cbuild2 scaffolding for building remote chroots for glibc testing.
* Add glibc multi-lib builds and IFUNC system libraries.
* Work on cbuild2 support for local tar files.

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ACTIVITY] Week 3 (Jan 13-17 2014)

[Ryan Arnold]

== Progress ==
* Cbuildv2 fix for *_release() functions which were changing out of
the build directory but then not changing back to the builddir, which
caused problems with paths relative to the builddir. (1/10)

* TCWG-340 Enable Glibc remote testsuite integration - (7/10)
- Working with upstream community on scoping and designing remote
testsuite integration.
- Setting up arm chroot environment on chromebook with documentation
on how to make this reproduceable.

* TCWG-352 AArch64 clone is missing some CFI markup - (2/10)
- Setup aarch64 environment for testing and built static clone tests
to test the patch.

== Plan ==

* Start implementing (code) for glibc remote testsuite integration.

== Issues ==

None

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ACTIVITY] Jan 20 - 24 - 2014

[Ryan Arnold]

== Progress ==

Deferred US Holiday (MLK day) from Monday to Tuesday

* Debugged what was thought to be a cbuild2 problem but ended up being
due to default enablement of multilib in gcc. (2/10)

* Started working on adding mulit-lib support to cbuild2 (minimal
configuration for installing headers). (8/10) [Jira card forthcoming]

 - Moved kernel headers installation to arch based directory in
sysroot and then symlinked appropriate host include directories to
common arch directories.

 - Figured out how to build multilib arm libraries for
arm-none-linux-gnueabihf and arm-none-linux-gnueabi.

== Plan ==

* Add cbuild2 scripting to build multilib libraries based on gcc
-print-multi-lib

* Figure out how to get gcc to select the correct multilib headers
directory so that we don't need a merged include directory.

== Issues ==
 * None

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

Re: linaro/eglibc 2.19

[Ryan Arnold]

On Wed, Feb 19, 2014 at 5:32 PM, Khem Raj  wrote:
> I wanted to know if there is a 2.19 head for linaro eglibc being created ?
> in that case that bbappend needs fixing too.
>
> Thanks
> -Khem

Hi Khem,

Since glibc 2.19 just posted we have not yet spun an eglibc release
within Linaro.

We'll do that soon.

-- 
Ryan S. Arnold
Linaro Toolchain Working Group
www.linaro.org

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

Re: [ACTIVITY] 10-14 FEB 2014

[Ryan Arnold]

Hi Kugan, in the future it'd help me immensely if you could reference
the Jira Issue that's related to your investigations/work.  If there
isn't one, then we should be creating them.

Thanks!  Ryan

On Sun, Feb 16, 2014 at 5:31 PM, Kugan
 wrote:
> == Progress ==
>  - vectorizer (7/10)
>- Looked into vectorizer target-hooks
>- enablement of half-float for vectorising; dropped the patch after
> discussing
>- Started analysing code generated with unlimited model
>  - gcc 4.8 regression (1/10)
>- Built Novemnebr and December release (native with system libc)
>- Ran spec2k fp. Can see regression for ammp with -O3 (with
> -march=armv7-a and -mthumb)
>   -Started bisecting
>
>  - Chromebook reset-up (2/10)
>- SD card died and setup again
>- Using hdd for gcc testing
>
> == Plan ==
>  - Check ARMv5 regression for unaligned access
>  - Look into vectorizer cost model/benchmarking
>
> ___
> linaro-toolchain mailing list
> linaro-toolchain@lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-toolchain



-- 
Ryan S. Arnold
Linaro Toolchain Working Group
www.linaro.org

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

Re: [ACTIVITY] 10-14 FEB 2014

[Ryan Arnold]

James told me that he'd like to see a Jira card for anything that
takes over 4 hours of work.  This can include bugs if they don't
easily fit under another card.

In the meantime, the issue/bug ids would help as well.  I'm not
familiar enough with everyone's work yet to know how to find these
myself.

Thanks Kugan!

On Wed, Feb 19, 2014 at 11:03 PM, Kugan
 wrote:
> Hi Ryan,
>
> I don’t have any JIRA tickets created for these issues/bugs (there are
> launchpad bug entries). Do you want me to create JIRA tickets when there
> isn’t any?
>
> Thanks,
> Kugan
>
> On 20/02/14 15:48, Ryan Arnold wrote:
>> Hi Kugan, in the future it'd help me immensely if you could reference
>> the Jira Issue that's related to your investigations/work.  If there
>> isn't one, then we should be creating them.
>>
>> Thanks!  Ryan
>>
>> On Sun, Feb 16, 2014 at 5:31 PM, Kugan
>>  wrote:
>>> == Progress ==
>>>  - vectorizer (7/10)
>>>- Looked into vectorizer target-hooks
>>>- enablement of half-float for vectorising; dropped the patch after
>>> discussing
>>>- Started analysing code generated with unlimited model
>>>  - gcc 4.8 regression (1/10)
>>>- Built Novemnebr and December release (native with system libc)
>>>- Ran spec2k fp. Can see regression for ammp with -O3 (with
>>> -march=armv7-a and -mthumb)
>>>   -Started bisecting
>>>
>>>  - Chromebook reset-up (2/10)
>>>- SD card died and setup again
>>>- Using hdd for gcc testing
>>>
>>> == Plan ==
>>>  - Check ARMv5 regression for unaligned access
>>>  - Look into vectorizer cost model/benchmarking
>>>
>>> ___
>>> linaro-toolchain mailing list
>>> linaro-toolchain@lists.linaro.org
>>> http://lists.linaro.org/mailman/listinfo/linaro-toolchain
>>
>>
>>



-- 
Ryan S. Arnold
Linaro Toolchain Working Group
www.linaro.org

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

Re: Building 4.8 without multilib

[Ryan Arnold]

On Wed, Mar 5, 2014 at 8:01 AM, Diane Holt  wrote:
> Is that supposed to be possible? When I add --disable-multilib to the
> configure options, the build fails on the install, because it hasn't built
> any of src/gcc-linaro-4.8-2014.02/libgcc:
>
> /bin/sh ../../../../src/gcc-linaro-4.8-2014.02/libgcc/../mkinstalldirs
> /home/ubuntu/work483/build/sysroot/home/ubuntu/opt/cross-gcc-linaro/lib/gcc/arm-linux-gnueabi/4.8.3
> /usr/bin/install -c -m 644 libgcc_eh.a
> /home/ubuntu/work483/build/sysroot/home/ubuntu/opt/cross-gcc-linaro/lib/gcc/arm-linux-gnueabi/4.8.3/
> /usr/bin/install: cannot stat `libgcc_eh.a': No such file or directory
> make[3]: *** [install-shared] Error 1
> make[3]: Leaving directory
> `/home/ubuntu/work483/build/gcc/arm-linux-gnueabi/libgcc'
> make[2]: *** [install-target-libgcc] Error 2
> make[2]: Leaving directory `/home/ubuntu/work483/build/gcc'
> make[1]: *** [install] Error 2
> make[1]: Leaving directory `/home/ubuntu/work483/build/gcc'
> make: *** [stamp/gcc-install] Error 2
>
> I don't want or need multilib, so I'd rather build the toolchain without it,
> but before I try to make that happen, I wanted to make sure it's supposed to
> be able to get built correctly that way.
>
> Thanks,
> Diane

Diane,

I ran into this issue as well, and believe that it's related to your
sysroot lacking the proper soft-float headers and/or missing kernel
headers.

This means that your sysroots include/ directory needs to be prepared
for multi-lib headers before you do a multi-lib enabled gcc build.

So, what I did was identify the multi-lib configurations that are
enabled when I selected a particular --target.

Take that information and build the kernel headers for all
configurations and install those headers into the sysroot include
directory.

Then build a glibc version for each configuration and install the
headers into the sysroot.

Then you might need to inform GCC where the include directories are
(though a properly formatted multi-lib sysroot should be automatically
detected when you pass the sysroot switch).

Zhenqiang Chen knows about this process a bit better than I do.

-- 
Ryan S. Arnold
Linaro Toolchain Working Group
www.linaro.org

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

Re: Using binfmt_misc for cross testing

[Ryan Arnold]

On Wed, May 21, 2014 at 5:54 AM, Bernie Ogden wrote:

> If we add models as targets then that alleviates the sharing problem a
> bit - for test runs that aren't going to be too slow on models. And
> you'll need to watch out for nested '"' in $@, but I guess you know
> that.
>

Ultimately we need to validate on real hardware.  From a release
perspective it's necessary.  From a development perspective being able to
validate with models is effective until you need to have the final
validation.


> I guess this approach is similar to what 'make check
> test-wrapper="./glibc/scripts/cross-test-ssh.sh hostname"' is
> supposed to do for glibc. Ryan mentioned that glibc cross-test doesn't
> work, and it certainly fell over when I tried it. That makes me wonder
> whether there are hidden difficulties here, but that vague bit of
> evidence aside, the approach sounds sensible to me.
>

It's not that it doesn't work.  It's just that it's complicated to setup
because it involves setting up a network file system.


> On 21 May 2014 07:46, Kugan  wrote:
> >
> >
> > On 21/05/14 16:08, Maxim Kuvyrkov wrote:
> >> I have been thinking how to simplify cross-testing our toolchain for
> both automated and development/debugging builds, and among various options
> the most universal I came up with is ARM hardware + ssh + binfmt_misc +
> sshfs.  I wonder if anyone has already tried this or can suggest
> alternatives which are as universal.
> >>
> >> Given:
> >> - host x86_64 development machine
> >> - cross-compiler
> >> - target hardware with fast network to the host
> >> - host and target have ssh
> >> - testsuite (gcc/glibc/gdb/etc)
> >>
> >> Here is how it is going to work
> >>
> >> 1. On host we create a simple wrapper script that will pass through its
> arguments as command to execute on target via ssh:
> >> ===
> >> #!/bin/sh
> >> ssh -p 22NN $TARGET_BOARD "$@"
> >> ===
> >>
> >> 2. We register this script in binfmt_misc to be used as interpreter for
> target binaries.  Value of $TARGET_BOARD will be picked up from the
> environment and can be set to different boards for different testsuite runs.
> >>
> >> 3. The target board needs to be prepared for a particular testsuite run:
> >>   -- Runtime libraries need to be either copied or mounted via sshfs
> from the host.  It is an open question how best to install several sets of
> libraries (for parallel runs) so that each set appears to be main system
> libraries.  My current thinking is a separate ssh server inside chroot per
> each test run.
> >>   -- Test directory needs to be sshfs mounted on target from host so
> that the target could see test executables.
> >>   -- Preparation/finalization of the board can either be done
> explicitly before/after testing.  Or it can be done on demand by the
> aforementioned script: the script checks whether a multiplexed ssh socket
> exists, and, if not, it prepares the board and starts a multiplexed ssh
> connection.
> >>
> > Is this set-up for NX? Issue is how do we share the target board between
> > different users? We can of-course initiate a lava hacking session but
> > the amount of time we will have to wait to get the session active might
> > be too long depending on the target classes availability.
> >
> > Thanks
> > Kugan
> >
> >> 4. Testing is fired up as if it is normal "native" testing.  Whenever
> kernel is given an ARM binary to execute -- it passes it off to wrapper,
> which passes it off to the target board via ssh.  The board sees same
> filesystem as host and happily executes binaries against toolchain runtime
> libraries.
> >>
> >> Comments or rotten tomatoes?
> >>
> >> Thank you,
> >>
> >> --
> >> Maxim Kuvyrkov
> >> www.linaro.org
> >>
> >>
> >>
> >>
> >> ___
> >> linaro-toolchain mailing list
> >> linaro-toolchain@lists.linaro.org
> >> http://lists.linaro.org/mailman/listinfo/linaro-toolchain
> >>
> >
> > ___
> > linaro-toolchain mailing list
> > linaro-toolchain@lists.linaro.org
> > http://lists.linaro.org/mailman/listinfo/linaro-toolchain
>
> ___
> linaro-toolchain mailing list
> linaro-toolchain@lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-toolchain
>



-- 
Ryan S. Arnold
Linaro Toolchain Working Group - Engineering Manager
www.linaro.org
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

Re: [ACTIVITY] 16 - 20 June

[Ryan Arnold]

On Mon, Jun 23, 2014 at 9:34 AM, Charles Baylis 
wrote:

> * Linaro bugzilla #24  - [6/10]
>   * investigating cause of ICE in Linaro 4.9
>
> * PR61411 [1/10]
>
> * Committed patches for division (TCWG-???) and Neon address mode
> (TCWG-430) [1/10]
>

For reference:

https://cards.linaro.org/browse/TCWG-293


>
> * Admin [1/10]
>
> * Holiday [1/10]
>
> ___
> linaro-toolchain mailing list
> linaro-toolchain@lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-toolchain
>

-- 
Ryan S. Arnold
Linaro Toolchain Working Group - Engineering Manager
www.linaro.org
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

Linaro Lab Maintenance impacts to the November Toolchain Quarterly release

[Ryan Arnold]

Hi All,

There will be lab downtime in the month of November, and rather than
jeopardize the November quarterly binary toolchain release we've decided to
take some steps to ensure that it takes place on time.

The November binary toolchain quarterly release will contain some ARM64
erratum fixes.  These are already in the Linaro GCC 4.9 2014.10 source
package release.

The November binary toolchain quarterly release will contain these fixes,
and will be delivered as planned, but will be based on the Linaro GCC 4.9
2014.10 package.  We will not have a November Linaro GCC 4.9 2014.11 source
package release.

The December release will be the next Linaro GCC 4.9 source package release.

-- 
Ryan S. Arnold
Linaro Toolchain Working Group - Engineering Manager
www.linaro.org
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

Re: [ACTIVITY] 2-6 February 2015

[Ryan Arnold]

On Fri, Feb 6, 2015 at 7:41 AM, Christophe Lyon 
wrote:

> == Progress ==
> * GCC trunk/4.9 monitoring
>
> * Neon intrinsics tests
>   - committed the last patch of the 2nd series.
>   - about another 1/3 of the tests remain to be converted: will wait
> for GCC stage1
>

For future reference, please put the (TCWG-*) next to the title so I can
easily cross correlate it, e.g.,

* Neon intrinsics tests (TCWG-537)

In reference to:

NEON intrinsics testsuite for GCC (TCWG-537
)


>
> * AArch64 sanitizers (2/10)
>   - Renato committed my patches to enable ASAN in LLVM/AArch64
>   - the official aarch64 buildbot (Juno) had problems after these, so
> the asan tests are disabled again until the problem is understood.
> Probable board configuration problem, since the tests passed on our
> Juno.
>   - preparing a patch to solve the long standing issue with dependency
> on aarch64 kernel version (kernel_old_[ug]id)
>

This should have a blueprint, so I created one:

Decouple ASAN from hardcoded kernel version (TCWG-630
)

Please update the title if it's not correct.



> * Backports (4/10)
>   - reviews
>   - respawned validations under MergeFarm
>
> * ABE:
>   - improving reporting
>
> * Misc (4/10)
>   - meetings, conf-calls, emails, 
>
> == Next ==
> Connect, then holidays
>
> ___
> linaro-toolchain mailing list
> linaro-toolchain@lists.linaro.org
> http://lists.linaro.org/mailman/listinfo/linaro-toolchain
>



-- 
Ryan S. Arnold
Linaro Toolchain Working Group - Engineering Manager
www.linaro.org
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

Re: GDB Build Error: No rule to make target `-L../zlib'

[Ryan Arnold]

On Wed, Apr 1, 2015 at 9:35 AM, Christopher Covington 
wrote:

> Hi,
>
> I'm seeing the following build error trying to build from the current
> master
> branch (1ac806b) of http://git.linaro.org/toolchain/binutils-gdb.
>
> make[3]: *** No rule to make target `-L../zlib', needed by `run'.  Stop.
> make[3]: *** Waiting for unfinished jobs
> make[3]: Leaving directory `gdb/sim/arm'
>
> The following commit predating the zlib changes appears to build without
> error.
>
> b19a8f8545100a08ee2a64c05631aff6f651faa1
>
> Thanks,
> Chris
>
> --
> Qualcomm Innovation Center, Inc.
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> a Linux Foundation Collaborative Project
> ___
> linaro-toolchain mailing list
> linaro-toolchain@lists.linaro.org
> https://lists.linaro.org/mailman/listinfo/linaro-toolchain
>

Hi Christopher,

If you feel this is a bug in the Linaro Toolchain's GDB branch please file
a bug at bugs.linaro.org and we'll take a look.

-- 
Ryan S. Arnold
Linaro Toolchain Working Group - Engineering Manager
www.linaro.org
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

Linaro Toolchain Product Release Process Changes (Effective 2015.04)

[Ryan Arnold]

Hello,

In an effort to provide a longer quality control window for quarterly
releases the Linaro Toolchain Working Group will be making some changes to
the release process starting with the forthcoming 2015.04 products.

Little will change for the consumers of TCWG products.

The current monthly source release of the 'stable' Linaro GCC source
archives posted to releases.linaro.org will move to snapshots.linaro.org
and will be designated 'monthly snapshots'.

The exact location will be announced when the 2015.04 Toolchain component
source archive release notes are posted to this mailing list.

These monthly snapshots will continue to have branch merges, performance
fixes, security fixes, and correctness fixes applied on a monthly basis.
They will also continue to have validation across a variety of common ARM
targets performed (per backport) against them.

TCWG will introduce the concept of a 'release candidate source archive' and
'release candidate binary toolchain archive' six weeks before the projected
release date of the Quarterly Binary Toolchain Release.  For example, the
2015.05 Quarterly Binary Toolchain and Quarterly Source Archive will be
based upon the 2015.04 source archive snapshot.

Release candidate source and binary archives will be posted to
snapshots.linaro.org.

This release candidate will receive the scrutiny of internal and external
stakeholders for six weeks and give an opportunity to evaluate the
forth-coming Quarterly Binary Toolchain Archive and Source Archive
Release.  Problems found with the release candidates will result in the
availability of incremental release candidate archives.

The official quarterly release will be posted to releases.linaro.org.

Please direct any questions or concerns to this mailing list or to me
directly.

-- 
Ryan S. Arnold
Linaro Toolchain Working Group - Engineering Manager
www.linaro.org
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

Re: Linaro Toolchain Product Release Process Changes (Effective 2015.04)

[Ryan Arnold]

On Mon, Apr 20, 2015 at 11:16 AM, Ramana Radhakrishnan <
ramana.radhakrish...@arm.com> wrote:
>
> The current monthly source release of the 'stable' Linaro GCC source
>> archives posted to releases.linaro.org  will
>> move to snapshots.linaro.org  and will be
>> designated 'monthly snapshots'.
>>
>>
> Along with this monthly source snapshot - just to be explicit, will Linaro
> also provide binaries produced from the source tarball ?
>

Linaro currently does not provide a monthly binary archive for the monthly
source archive.  The binary archives are available on a quarterly cadence
only.  We will continue the same policy when the monthly source archives
move to snapshots.linaro.org.

-- 
Ryan S. Arnold
Linaro Toolchain Working Group - Engineering Manager
www.linaro.org
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

Re: Linaro Toolchain Product Release Process Changes (Effective 2015.04)

[Ryan Arnold]

On Tue, Apr 21, 2015 at 7:58 AM, Bernie Ogden 
wrote:

> > TCWG will introduce the concept of a 'release candidate source archive'
> and
> > 'release candidate binary toolchain archive' six weeks before the
> projected
> > release date of the Quarterly Binary Toolchain Release.  For example, the
> > 2015.05 Quarterly Binary Toolchain and Quarterly Source Archive will be
> > based upon the 2015.04 source archive snapshot.
> >
> > Release candidate source and binary archives will be posted to
> > snapshots.linaro.org.
>
> So the 'release candidate binary toolchain archive' will be in the
> form of source, or of binary tarball? My guess would be that, if
> binary toolchain users are going to look at a prerelease at all,
> they'll only do so if it's already built for them.
>

Both.  There will be a tarball archive for the sources as well as the
binaries.

-- 
Ryan S. Arnold
Linaro Toolchain Working Group - Engineering Manager
www.linaro.org
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

Re: ABE - bug in copy_gcc_libs_to_sysroot() while building native toolchain for aarch64

[Ryan Arnold]

On Mon, Jul 27, 2015 at 10:41 AM, Jim Wilson  wrote:

> On Sun, Jul 26, 2015 at 11:36 PM, Virendra Kumar Pathak
>  wrote:
> > In copy_gcc_libs_to_sysroot()  - which copy libgcc.a to sysroot, current
> > implementation try to find the absolute path of libgcc.a as below :
> > libgcc="`${local_builds}/destdir/${host}/bin/${target}-gcc
> > -print-file-name=${libgcc}`
>
> The easy solution is to change ${host} to ${build}, here and immediately
> above.
>

I've been looking for the source of this bug for ages.  Thanks Virendra and
Jim!  I'll take a look.

-- 
Ryan S. Arnold
Linaro Toolchain Working Group - Engineering Manager
www.linaro.org
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 5.1 2015.08-rc2

[Ryan Arnold]

The Linaro Toolchain Working Group is pleased to announce the availability
of the Linaro Stable Binary Toolchain Release-Candidate GCC 5.1-2015.08-rc2
Archives.

  http://snapshots.linaro.org/components/toolchain/binaries/5.1-2015.08-rc2/

These archives provide cross-toolchain executables (compiler, debugger,
linker, etc.) and shared libraries (libstdc++, libc, etc.) that target ARM
or Aarch64 GNU/Linux and bare-metal environments. The cross-toolchain
binaries execute on a Linux or MS Windows (under mingw32) host
operating-system.

Please evaluate this release-candidate for correctness.  Linaro will
shortly spin the Linaro GCC 5.1-2015.08 release if this release-candidate
passes stakeholder validation.

For bugs related to this release-candidate please email
linaro-toolchain@lists.linaro.org or file a bug at http://
https://bugs.linaro.org/enter_bug.cgi?product=Linux%20Binary%20toolchain

NEWS

* 2015.08-rc2

* The Linaro 2015.08-rc2 release-candidate binary toolchain is based on
the Linaro GCC-5.1-2015.08-rc1 release-candidate source archive. The only
changes between 2015.08-rc1 and 2015.08-rc2 were the following changes in
how the binary toolchains were built. The compiler itself was not changed.

* x86_64 hosted, armv8l-linux-gnueabihf targetted cross toolchains are
now correctly configured. This was broken in 2015.08-rc1. The
cross-compiler targetting armv8l-linux-gnueabihf is now correctly
configured with --with-arch=armv8-a --with-fpu=neon-fp-armv8
--with-float=hard --disable-multilib --enable-multiarch.

* Glibc’s slibdir and libdir were once again modified to address Linaro
Bugzilla 1717 – Linaro-4.9-2015.05 moved system libs from /libc/lib/ to
/libc/usr/lib/ which breaks things. The following are now the correct
locations:
libdir=lib/ (linker-scripts and static archives)
slibdir=usr/lib/ (shared objects)
rtlddir=lib/ (dynamic linker)

* 2015.08-rc1

* x86_64 hosted, armv8l-linux-gnueabihf targetted cross toolchain now
provided.

Delivering on REQ-477 – Enable x86_64 to Aarch32 (32-bit ARMv8-A)
cross binary toolchain product release and CARD-1637 – Enable Aarch32
(32-bit ARMv8-A) cross binary toolchain product releases ,
armv8l-linux-gnueabihf targetted toolchains are now available as part of
this release-candidate.

* Python support in GDB for both Linux and Mingw32 (32-bit windows).

Delivered as requested in the linaro-toolchain mailing list post
title – windows binary builds with gdb-python enabled?.

* Added missing expat support to GDB.

This addresses the following linaro-toolchain mailing list post –
"Missing expat support in GDB 7.8 multi-lib enablement for arm bare-metal
targets."

* A fix for multilib enablement in baremetal toolchains (as described
in ABE Review 6862).

* Library Paths are now congruent with older Linaro Toolchain path
layouts. This addresses Linaro Bugzilla 1717 – Linaro-4.9-2015.05 moved
system libs from /libc/lib/ to /libc/usr/lib/ which breaks things.
libdir=lib/ (shared objects)
slibdir=usr/lib/ (static libraries)
rtlddir=lib/ (dynamic linker)
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ANNOUNCE] Linaro Binary Toolchain Release GCC 5.1 2015.08

[Ryan Arnold]

The Linaro Toolchain Working Group is pleased to announce the availability
of the Linaro Stable Binary Toolchain GCC 5.1-2015.08 Archives.

  http://releases.linaro.org/components/toolchain/binaries/5.1-2015.08/

These archives provide cross-toolchain executables (compiler, debugger,
linker, etc.) and shared libraries (libstdc++, libc, etc.) that target ARM
or Aarch64 GNU/Linux and bare-metal environments. The cross-toolchain
binaries execute on a Linux or MS Windows (under mingw32) host
operating-system.

For bugs related to this release please email
linaro-toolchain@lists.linaro.org or file a bug at
https://bugs.linaro.org/enter_bug.cgi?product=Linux%20Binary%20toolchain

NEWS

* 2015.08

  * The Linaro GCC 5.1 2015.08 binary toolchain release is based on the Linaro
GCC-5.1-2015.08 source archive release
.
The major changes contained in 2015.08 over 2015.05 are described in the
sections below on 2015.08-rc1 and 2015.08-rc2 .

* 2015.08-rc2

* The Linaro 2015.08-rc2 release-candidate binary toolchain is based on
the Linaro GCC-5.1-2015.08-rc1 release-candidate source archive. The only
changes between 2015.08-rc1 and 2015.08-rc2 were the following changes in
how the binary toolchains were built. The compiler itself was not changed.

* x86_64 hosted, armv8l-linux-gnueabihf targetted cross toolchains are
now correctly configured. This was broken in 2015.08-rc1. The
cross-compiler targetting armv8l-linux-gnueabihf is now correctly
configured with --with-arch=armv8-a --with-fpu=neon-fp-armv8
--with-float=hard --disable-multilib --enable-multiarch.

* Glibc’s slibdir and libdir were once again modified to address
Linaro Bugzilla
1717 – Linaro-4.9-2015.05 moved system libs from /libc/lib/ to
/libc/usr/lib/ which breaks things. The following are now the correct
locations:
libdir=lib/ (linker-scripts and static archives)
slibdir=usr/lib/ (shared objects)
rtlddir=lib/ (dynamic linker)

* 2015.08-rc1

* x86_64 hosted, armv8l-linux-gnueabihf targetted cross toolchain now
provided.

Delivering on REQ-477 – Enable x86_64 to Aarch32 (32-bit ARMv8-A)
cross binary toolchain product release and CARD-1637 – Enable Aarch32
(32-bit ARMv8-A) cross binary toolchain product releases ,
armv8l-linux-gnueabihf targetted toolchains are now available as part of
this release-candidate.

* Python support in GDB for both Linux and Mingw32 (32-bit windows).

Delivered as requested in the linaro-toolchain mailing list post
title – windows binary builds with gdb-python enabled?.

* Added missing expat support to GDB.

This addresses the following linaro-toolchain mailing list post –
"Missing expat support in GDB 7.8 multi-lib enablement for arm bare-metal
targets."

* A fix for multilib enablement in baremetal toolchains (as described
in ABE Review 6862).

* Library Paths are now congruent with older Linaro Toolchain path
layouts. This addresses Linaro Bugzilla 1717 – Linaro-4.9-2015.05 moved
system libs from /libc/lib/ to /libc/usr/lib/ which breaks things.
libdir=lib/ (shared objects)
slibdir=usr/lib/ (static libraries)
rtlddir=lib/ (dynamic linker)

-- 
Ryan S. Arnold
Linaro Toolchain Working Group - Engineering Manager
www.linaro.org
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 5.2 2015.11-rc1

[Ryan Arnold]

The Linaro Toolchain Working Group is pleased to announce the availability
of the Linaro  Stable  Binary Toolchain  GCC  5.2-2015.11-rc1
Release-Candidate Archives.

 http://snapshots.linaro.org/components/toolchain/binaries/5.2-2015.11-rc1/

http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.2-2015.11-rc1/

These archives provide cross-toolchain executables (compiler, debugger,
linker, etc.) and shared libraries (libstdc++, libc, etc.) that target  ARM
 or Aarch64 GNU/Linux and bare-metal environments.  The cross-toolchain
binaries execute on a Linux or MS Windows (under mingw32) host
operating-system.

Please evaluate this release-candidate for correctness.  Linaro will
shortly spin the Linaro  GCC  5.2-2015.11 release if this release-candidate
passes stakeholder validation.

For bugs related to this release-candidate please email
linaro-toolchain@lists.linaro.org or file a bug at
https://bugs.linaro.org/enter_bug.cgi?product=Linux%20Binary%20toolchain

 NEWS

* GCC  5.2 2015.11-rc1

The Linaro  GCC  5.2 2015.11-rc1 binary toolchain release-candidate is
built from the  Linaro GCC-5.2-2015.11  release-candidate source archive.
The Linaro GCC-5.2-2015.11 release source archive is derived from the same
sources as the  Linaro GCC-5.2-2015.10  snapshot source archive.

-- 
Ryan S. Arnold
Linaro Toolchain Working Group - Engineering Manager
www.linaro.org
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ANNOUNCE] Linaro Binary Toolchain Release GCC 5.2 2015.11

[Ryan Arnold]

The Linaro Toolchain Working Group is pleased to announce the availability
of the Linaro Stable Binary Toolchain GCC 5.2-2015.11 Release Archives.

 http://releases.linaro.org/components/toolchain/binaries/5.2-2015.11/
 http://releases.linaro.org/components/toolchain/gcc-linaro/5.2-2015.11/

These archives provide cross-toolchain executables (compiler, debugger,
linker, etc.) and shared libraries (libstdc++, libc, etc.) that target ARM
or Aarch64 GNU/Linux and bare-metal environments.  The cross-toolchain
binaries execute on a Linux or MS Windows (under mingw32) host
operating-system.

Please evaluate this release-candidate for correctness.  Linaro will
shortly spin the Linaro GCC 5.2-2015.11 release if this release-candidate
passes stakeholder validation.

For bugs related to this release-candidate please email
linaro-toolchain@lists.linaro.org or file a bug at
https://bugs.linaro.org/enter_bug.cgi?product=Linux%20Binary%20toolchain

NEWS

* GCC 5.2 2015.11

The Linaro GCC 5.2 2015.11 binary toolchain release is built from the
Linaro GCC-5.2-2015.11 release source archive.  The Linaro GCC-5.2-2015.11
release source archive is derived from the same sources as the Linaro
GCC-5.2-2015.10 snapshot source archive.

* GCC 5.2 2015.11-rc1

The Linaro GCC 5.2 2015.11-rc1 binary toolchain release-candidate is built
from the Linaro GCC-5.2-2015.11 release-candidate source archive. The
Linaro GCC-5.2-2015.11-rc1 release-candidate source archive is derived from
the same sources as the Linaro GCC-5.2-2015.10 snapshot source archive.

-- 
Ryan S. Arnold
Linaro Toolchain Working Group - Engineering Manager
www.linaro.org
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

Re: why ld.so in arm-linux-gnueabihf- toolchains search so many paths ?

[Ryan Arnold]

On Tue, Dec 1, 2015 at 1:24 AM, Barry Song <21cn...@gmail.com> wrote:

> hi guys,
> sorry maybe my question is stupid as i am not a toolchain guy.
>
> i have no idea why ld.so search so many paths. for example, put
> "-rpath" with /home/cnb1szh/test in a simple test program. then during
> dynamic linking at runtime, we get the below linking debug
> information:
>
> 30693: find library=libmytest.so [0]; searching
>
> 30693: search
> path=/home/cnb1szh/test/tls/v7l/neon/vfp:/home/cnb1szh/test/tls/v7l/neon:/home/cnb1szh/test/tls/v7l/vfp:/home/cnb1szh/test/tls/v7l:/home/cnb1szh/test/tls/neon/vfp:/home/cnb1szh/test/tls/neon:/home/cnb1szh/test/tls/vfp:/home/cnb1szh/test/tls:/home/cnb1szh/test/v7l/neon/vfp:/home/cnb1szh/test/v7l/neon:/home/cnb1szh/test/v7l/vfp:/home/cnb1szh/test/v7l:/home/cnb1szh/test/neon/vfp:/home/cnb1szh/test/neon:/home/cnb1szh/test/vfp:/home/cnb1szh/test
> (RPATH from file ./hello)
>
> 30693: trying file=/home/cnb1szh/test/tls/v7l/neon/vfp/libmytest.so
>
> 30693: trying file=/home/cnb1szh/test/tls/v7l/neon/libmytest.so
>
> 30693: trying file=/home/cnb1szh/test/tls/v7l/vfp/libmytest.so
>
> 30693: trying file=/home/cnb1szh/test/tls/v7l/libmytest.so
>
> 30693: trying file=/home/cnb1szh/test/tls/neon/vfp/libmytest.so
>
> 30693: trying file=/home/cnb1szh/test/tls/neon/libmytest.so
>
> 30693: trying file=/home/cnb1szh/test/tls/vfp/libmytest.so
>
> 30693: trying file=/home/cnb1szh/test/tls/libmytest.so
>
> 30693: trying file=/home/cnb1szh/test/v7l/neon/vfp/libmytest.so
>
> 30693: trying file=/home/cnb1szh/test/v7l/neon/libmytest.so
>
> 30693: trying file=/home/cnb1szh/test/v7l/vfp/libmytest.so
>
> 30693: trying file=/home/cnb1szh/test/v7l/libmytest.so
>
> 30693: trying file=/home/cnb1szh/test/neon/vfp/libmytest.so
>
> 30693: trying file=/home/cnb1szh/test/neon/libmytest.so
>
> 30693: trying file=/home/cnb1szh/test/vfp/libmytest.so
>
> 30693: trying file=/home/cnb1szh/test/libmytest.so
>
>
> but we don't have /home/cnb1szh/test/tls/, /home/cnb1szh/test/v7l/,
> /home/cnb1szh/test/vfp/, /home/cnb1szh/test/neon/, why does the ld.so
> search so many paths?
>
>
> -barry
> ___
> linaro-toolchain mailing list
> linaro-toolchain@lists.linaro.org
> https://lists.linaro.org/mailman/listinfo/linaro-toolchain
>


Hi Barry, this is a known, intentional behavior of the dynamic-linker.

It defaults to searching for libraries in a tls directory (the glibc
developers intend to remove this since linux-threads are now gone and nptl
is the standard but no-one has stepped forward to do so), then directories
based on the cpu, then directories that are based on the hardware
capabilities for the platform (AT_HWCAP for 'arm') in various
combinations.  This is why you see it searching the different variations of
directories.

This is not a bug.

What this does is allows the Linux distribution to provide optimized
versions of the libraries in each of those directories.  The optimized
versions of the library have the most efficient code-gen for the capability
present.  For instance, in your own library, if you wanted to have a neon
optimized version and a non-neon optimized version you'd put the neon one
in test/neon/ and the non-optimized version in test/ directly.

-- 
Ryan S. Arnold
Linaro Toolchain Working Group - Engineering Manager
www.linaro.org
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 5.2 2015.11-2-rc1

[Ryan Arnold]

The Linaro Toolchain Working Group is pleased to announce the availability
of the Linaro Stable Binary Toolchain GCC 5.2-2015.11-2-rc1
Release-Candidate Archives.

http://snapshots.linaro.org/components/toolchain/binaries/5.2-2015.11-2-rc1/
http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.2-2015.11-2-rc1/

These archives provide cross-toolchain executables (compiler, debugger,
linker, etc.) and shared libraries (libstdc++, libc, etc.) that target ARM
or Aarch64 GNU/Linux and bare-metal environments. The cross-toolchain
binaries execute on a Linux or MS Windows (under mingw32) host
operating-system.

Please evaluate this release-candidate for correctness. Linaro will shortly
spin the Linaro GCC 5.2-2015.11-2 release if this release-candidate passes
stakeholder validation.

For bugs related to this release-candidate please email
linaro-toolchain@lists.linaro.org or file a bug at http://
https://bugs.linaro.org/enter_bug.cgi?product=Linux%20Binary%20toolchain

NEWS

* GCC 5.2 2015.11-2-rc1

The Linaro GCC 5.2 2015.11-2-rc1 binary toolchain release-candidate is
built from the Linaro GCC-5.2-2015.11-2-rc1 release-candidate source
archive. The Linaro GCC-5.2-2015.11-2-rc1 release-candidate source archive
is derived from the same sources as the Linaro GCC-5.2-2015.10 snapshot
source archive.
This release-candidate includes fixes for the following issues:

Linaro bug 1995 identified a problem where the installed sysroot was not in
the place that the compiler expected the sysroot to be located by default.
This is fixed in the Linaro GCC 5.2 2015.11-2-rc1 binary toolchain
release-candidate.

* GCC 5.2 2015.11-1

The Linaro GCC 5.2 2015.11-1 binary toolchain release is built from the
Linaro GCC-5.2-2015.11-1 release source archive. The Linaro
GCC-5.2-2015.11-1 release source archive is derived from the same sources
as the Linaro GCC-5.2-2015.10 snapshot source archive.
This release includes fixes for the issues specified in the Linaro GCC 5.2
2015.11-1-rc1 release-candidate.

* GCC 5.2 2015.11-1-rc1

The Linaro GCC 5.2 2015.11-1-rc1 binary toolchain release-candidate is
built from the Linaro GCC-5.2-2015.11-1-rc1 release-candidate source
archive. The Linaro GCC-5.2-2015.11-1-rc1 release-candidate source archive
is derived from the same sources as the Linaro GCC-5.2-2015.10 snapshot
source archive.
This release-candidate includes fixes for the following issues:

The arm-eabi-none multi-libs are now available in the toolchain sysroot as
a fix for Linaro bug 1920 and Linaro bug 1922 .
Linaro glibc 2.21 now provides ld-linux-aarch64_be.so.1 .
Linux 32-bit host binaries for the ARMv7 Linux hard float cross-toolchain
(arm-linux-gnueabihf triple).

* GCC 5.2 2015.11

The Linaro GCC 5.2 2015.11 binary toolchain release is built from the
Linaro GCC-5.2-2015.11 release source archive. The Linaro GCC-5.2-2015.11
release source archive is derived from the same sources as the Linaro
GCC-5.2-2015.10 snapshot source archive.

* GCC 5.2 2015.11-rc1

The Linaro GCC 5.2 2015.11-rc1 binary toolchain release-candidate is built
from the Linaro GCC-5.2-2015.11 release-candidate source archive. The
Linaro GCC-5.2-2015.11-rc1 release-candidate source archive is derived from
the same sources as the Linaro GCC-5.2-2015.10 snapshot source archive.

-- 
Ryan S. Arnold
Linaro Toolchain Working Group - Engineering Manager
www.linaro.org
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ANNOUNCE] Linaro Binary Toolchain Release Respin GCC 5.2 2015.11-2

[Ryan Arnold]

The Linaro Toolchain Working Group is pleased to announce the availability
of the Linaro Stable Binary Toolchain GCC 5.2-2015.11-2 Release Archives.

http://releases.linaro.org/components/toolchain/binaries/5.2-2015.11-2/
http://releases.linaro.org/components/toolchain/gcc-linaro/5.2-2015.11-2/

These archives provide cross-toolchain executables (compiler, debugger,
linker, etc.) and shared libraries (libstdc++, libc, etc.) that target ARM
or Aarch64 GNU/Linux and bare-metal environments. The cross-toolchain
binaries execute on a Linux or MS Windows (under mingw32) host
operating-system.

Please evaluate this release-candidate for correctness. Linaro will shortly
spin the Linaro GCC 5.2-2015.11-2 release if this release-candidate passes
stakeholder validation.
For bugs related to this release-candidate please email
linaro-toolchain@lists.linaro.org or file a bug at
https://bugs.linaro.org/enter_bug.cgi?product=Linux%20Binary%20toolchain

NEWS

* GCC 5.2 2015.11-2

The Linaro GCC 5.2 2015.11-2 binary toolchain release respin is built from
the Linaro GCC-5.2-2015.11-2 release source archive. The Linaro
GCC-5.2-2015.11-2 release source archive is derived from the same sources
as the Linaro GCC-5.2-2015.10 snapshot source archive.

This release includes fixes for the issues specified in the Linaro GCC 5.2
2015.11-2-rc1 release-candidate.

* GCC 5.2 2015.11-2-rc1

The Linaro GCC 5.2 2015.11-2-rc1 binary toolchain release-candidate is
built from the Linaro GCC-5.2-2015.11-2-rc1 release-candidate source
archive. The Linaro GCC-5.2-2015.11-2-rc1 release-candidate source archive
is derived from the same sources as the Linaro GCC-5.2-2015.10 snapshot
source archive.
This release-candidate includes fixes for the following issues:

Linaro bug 1995 identified a problem where the installed sysroot was not in
the place that the compiler expected the sysroot to be located by default.
This is fixed in the Linaro GCC 5.2 2015.11-2-rc1 binary toolchain
release-candidate.

* GCC 5.2 2015.11-1

The Linaro GCC 5.2 2015.11-1 binary toolchain release is built from the
Linaro GCC-5.2-2015.11-1 release source archive. The Linaro
GCC-5.2-2015.11-1 release source archive is derived from the same sources
as the Linaro GCC-5.2-2015.10 snapshot source archive.
This release includes fixes for the issues specified in the Linaro GCC 5.2
2015.11-1-rc1 release-candidate.

* GCC 5.2 2015.11-1-rc1

The Linaro GCC 5.2 2015.11-1-rc1 binary toolchain release-candidate is
built from the Linaro GCC-5.2-2015.11-1-rc1 release-candidate source
archive. The Linaro GCC-5.2-2015.11-1-rc1 release-candidate source archive
is derived from the same sources as the Linaro GCC-5.2-2015.10 snapshot
source archive.
This release-candidate includes fixes for the following issues:

The arm-eabi-none multi-libs are now available in the toolchain sysroot as
a fix for Linaro bug 1920 and Linaro bug 1922 .
Linaro glibc 2.21 now provides ld-linux-aarch64_be.so.1 .
Linux 32-bit host binaries for the ARMv7 Linux hard float cross-toolchain
(arm-linux-gnueabihf triple).

* GCC 5.2 2015.11

The Linaro GCC 5.2 2015.11 binary toolchain release is built from the
Linaro GCC-5.2-2015.11 release source archive. The Linaro GCC-5.2-2015.11
release source archive is derived from the same sources as the Linaro
GCC-5.2-2015.10 snapshot source archive.

* GCC 5.2 2015.11-rc1

The Linaro GCC 5.2 2015.11-rc1 binary toolchain release-candidate is built
from the Linaro GCC-5.2-2015.11 release-candidate source archive. The
Linaro GCC-5.2-2015.11-rc1 release-candidate source archive is derived from
the same sources as the Linaro GCC-5.2-2015.10 snapshot source archive.


-- 
Ryan S. Arnold
Linaro Toolchain Working Group - Engineering Manager
www.linaro.org
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 5.3-2016.02-rc1

[Ryan Arnold]

The Linaro Binary Toolchain


Release-Candidate Linaro GCC 5.3-2016.02-rc1 is now available.

Notice: All Linaro GCC 5 series toolchain users should migrate to the
latest version of the Linaro GCC 5 toolchain in order to mitigate
potential security exposure to CVE-2015-7545.  See the NEWS section
below for details.

Download release-candidate packages from:


http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.02-rc1/

http://snapshots.linaro.org/components/toolchain/binaries/5.3-2016.02-rc1/

Previous snapshots and release-candidates are at:

http://snapshots.linaro.org/components/toolchain/binaries/

Previous releases are at:

http://releases.linaro.org/components/toolchain/binaries/

Host Requirements
==

Linaro officially supports the current and previous Ubuntu LTS
releases (as of the time of this release).  This does not mean that
the toolchain will not work on other/older Linux distributions.  See
the following for the life-time of Ubuntu LTS releases.

https://wiki.ubuntu.com/Releases

The host system upon which the cross-compiler will run requires a
minimum of glibc 2.14, because of API changes to glibc's memcpy API.

https://bugs.linaro.org/show_bug.cgi?id=1869

Package Versions
=
Linaro GCC 5.3-2016.02-rc1

FSF glibc 2.21 (release/2.21)

Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch)

Linaro binutils 2.25 (linaro_binutils-2_25-branch)

FSF GDB 7.10 (gdb-7.10-branch)

Linaro toolchain package git branches are hosted at:

http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search

NEWS for Linaro GCC 5.3-2016.02-rc1


* Applied fix for CVE-2015-7545 - A stack-based buffer overflow in
  glibc's getaddrinfo() was corrected in glibc 2.23 and backported into
  glibc 2.21.

  https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html

* ARMv8.1 Instruction Support - ARMv8.1 instructions support was checked
  into GCC and binutils.   It has been backported into Linaro GCC 5.3
  and Linaro binutils 2.25.

* Backported -Bsymbolic-functions into Linaro binutils 2.25.

* Performance related backports from Linaro GCC 5.2-2015.11, Linaro GCC
  5.2-2015.12, and Linaro GCC 5.3-2016.01-1 have been included.

  See the following Linaro GCC snapshots:

  http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.2-2015.11/
  http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2015.12/
  http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.01-1/


Contact Linaro
===

File bugs at http://bugs.linaro.org

For Linaro member support see http://support.linaro.org

For Linaro community support email linaro-toolchain@lists.linaro.org

-- 
Ryan S. Arnold
Linaro Toolchain Working Group - Engineering Manager
www.linaro.org
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ANNOUNCE] Linaro Binary Toolchain Release GCC 5.3-2016.02

[Ryan Arnold]

The Linaro Binary Toolchain


The Linaro GCC 5.3-2016.02 Release is now available.

Notice: All Linaro GCC 5 series toolchain users should migrate to the
latest version of the Linaro GCC 5 toolchain in order to mitigate
potential security exposure to CVE-2015-7545.  See the NEWS section
below for details.

Download release packages from:


http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.02/

http://snapshots.linaro.org/components/toolchain/binaries/5.3-2016.02/

Previous snapshots and release-candidates are at:

http://snapshots.linaro.org/components/toolchain/binaries/

Previous releases are at:

http://releases.linaro.org/components/toolchain/binaries/

Host Requirements
==

Linaro officially supports the current and previous Ubuntu LTS
releases (as of the time of this release).  This does not mean that
the toolchain will not work on other/older Linux distributions.  See
the following for the life-time of Ubuntu LTS releases.

https://wiki.ubuntu.com/Releases

The host system upon which the cross-compiler will run requires a
minimum of glibc 2.14, because of API changes to glibc's memcpy API.

https://bugs.linaro.org/show_bug.cgi?id=1869

Package Versions
=
Linaro GCC 5.3-2016.02

FSF glibc 2.21 (release/2.21)

Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch)

Linaro binutils 2.25 (linaro_binutils-2_25-branch)

FSF GDB 7.10 (gdb-7.10-branch)

Linaro toolchain package git branches are hosted at:

http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search

NEWS for Linaro GCC 5.3-2016.02


* Applied fix for CVE-2015-7545 - A stack-based buffer overflow in
  glibc's getaddrinfo() was corrected in glibc 2.23 and backported into
  glibc 2.21.

  https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html

* ARMv8.1 Instruction Support - ARMv8.1 instructions support was checked
  into GCC and binutils.   It has been backported into Linaro GCC 5.3
  and Linaro binutils 2.25.

* Backported -Bsymbolic-functions into Linaro binutils 2.25.

* Performance related backports from Linaro GCC 5.2-2015.11, Linaro GCC
  5.2-2015.12, and Linaro GCC 5.3-2016.01-1 have been included.

  See the following Linaro GCC snapshots:


http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.2-2015.11/

http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2015.12/

http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.01-1/


Contact Linaro
===

File bugs at http://bugs.linaro.org

For Linaro member support see http://support.linaro.org

For Linaro community support email linaro-toolchain@lists.linaro.org

-- 
Ryan S. Arnold
Linaro Toolchain Working Group - Engineering Manager
www.linaro.org
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ANNOUNCE] Linaro Binary Toolchain Release GCC 5.3-2016.02 [Corrected Links]

[Ryan Arnold]

The Linaro Binary Toolchain


The Linaro GCC 5.3-2016.02 Release is now available.

Notice: All Linaro GCC 5 series toolchain users should migrate to the
latest version of the Linaro GCC 5 toolchain in order to mitigate
potential security exposure to CVE-2015-7545.  See the NEWS section
below for details.

Download release packages from:

http://releases.linaro.org/components/toolchain/gcc-linaro/5.3-2016.02/
http://releases.linaro.org/components/toolchain/binaries/5.3-2016.02/

Previous snapshots and release-candidates are at:

http://snapshots.linaro.org/components/toolchain/binaries/

Previous releases are at:

http://releases.linaro.org/components/toolchain/binaries/

Host Requirements
==

Linaro officially supports the current and previous Ubuntu LTS
releases (as of the time of this release).  This does not mean that
the toolchain will not work on other/older Linux distributions.  See
the following for the life-time of Ubuntu LTS releases.

https://wiki.ubuntu.com/Releases

The host system upon which the cross-compiler will run requires a
minimum of glibc 2.14, because of API changes to glibc's memcpy API.

https://bugs.linaro.org/show_bug.cgi?id=1869

Package Versions
=
Linaro GCC 5.3-2016.02

FSF glibc 2.21 (release/2.21)

Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch)

Linaro binutils 2.25 (linaro_binutils-2_25-branch)

FSF GDB 7.10 (gdb-7.10-branch)

Linaro toolchain package git branches are hosted at:

http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search

NEWS for Linaro GCC 5.3-2016.02


* Applied fix for CVE-2015-7545 - A stack-based buffer overflow in
  glibc's getaddrinfo() was corrected in glibc 2.23 and backported into
  glibc 2.21.

  https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html

* ARMv8.1 Instruction Support - ARMv8.1 instructions support was checked
  into GCC and binutils.   It has been backported into Linaro GCC 5.3
  and Linaro binutils 2.25.

* Backported -Bsymbolic-functions into Linaro binutils 2.25.

* Performance related backports from Linaro GCC 5.2-2015.11, Linaro GCC
  5.2-2015.12, and Linaro GCC 5.3-2016.01-1 have been included.

  See the following Linaro GCC snapshots:

  http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.2-2015.11/
  http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2015.12/
  http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.01-1/


Contact Linaro
===

File bugs at http://bugs.linaro.org

For Linaro member support see http://support.linaro.org

For Linaro community support email linaro-toolchain@lists.linaro.org
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 4.9-2016.02-rc1

[Ryan Arnold]

The Linaro Binary Toolchain


The Linaro GCC 4.9-2016.02-rc1 Release-Candidate is now available.

Notice: All Linaro GCC 4.9 series toolchain users should migrate to
the latest version of the Linaro GCC 4.9 toolchain in order to
mitigate potential security exposure to CVE-2015-7545.  See the NEWS
section below for details.

Download release-candidate packages from:


http://snapshots.linaro.org/components/toolchain/gcc-linaro/4.9-2016.02-rc1/

http://snapshots.linaro.org/components/toolchain/binaries/4.9-2016.02-rc1/

Previous snapshots and release-candidates are at:

http://snapshots.linaro.org/components/toolchain/binaries/

Previous releases are at:

http://releases.linaro.org/components/toolchain/binaries/

Host Requirements
==

Linaro officially supports the current and previous Ubuntu LTS
releases (as of the time of this release).  This does not mean that
the toolchain will not work on other/older Linux distributions.  See
the following for the life-time of Ubuntu LTS releases.

https://wiki.ubuntu.com/Releases

The host system upon which the cross-compiler will run requires a
minimum of glibc 2.14, because of API changes to glibc's memcpy API.

https://bugs.linaro.org/show_bug.cgi?id=1869

Package Versions
=
Linaro GCC 4.9-2016.02-rc1

FSF eglibc 2.19 (eglibc.git/linaro_eglibc-2_19)

Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch)

Linaro binutils 2.24 (linaro_binutils-2_24-branch)

FSF GDB 7.10 (gdb-7.10-branch)

Linaro Linux Version 3.17-2014.10 (linux-linaro-3.17-2014.10)

Linaro toolchain package git branches are hosted at:

http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search

NEWS for Linaro GCC 4.9-2016.02-rc1


* Applied fix for CVE-2015-7545 - A stack-based buffer overflow in
  glibc's getaddrinfo() was corrected in glibc 2.23 and backported into
  Linaro eglibc 2.19 (linaro_eglibc-2_19).

  https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html

* See the following Linaro GCC snapshot:

  http://snapshots.linaro.org/components/toolchain/gcc-linaro/4.9-2015.10/


Contact Linaro
===

File bugs at http://bugs.linaro.org

For Linaro member support see http://support.linaro.org

For Linaro community support email linaro-toolchain@lists.linaro.org


--

Ryan S. Arnold | Linaro Toolchain Engineering Manager
ryan.arn...@linaro.org | ryanarn on #linaro-tcwg @ freenode.irc.net
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ANNOUNCE] Linaro Binary Toolchain Release GCC 4.9-2016.02

[Ryan Arnold]

The Linaro Binary Toolchain


The Linaro GCC 4.9-2016.02 Release is now available.

Notice: All Linaro GCC 4.9 series toolchain users should migrate to
the latest version of the Linaro GCC 4.9 toolchain in order to
mitigate potential security exposure to CVE-2015-7545.  See the NEWS
section below for details.

Download release packages from:

http://releases.linaro.org/components/toolchain/gcc-linaro/4.9-2016.02/
http://releases.linaro.org/components/toolchain/binaries/4.9-2016.02/

Previous snapshots and release-candidates are at:

http://snapshots.linaro.org/components/toolchain/binaries/

Previous releases are at:

http://releases.linaro.org/components/toolchain/binaries/

Host Requirements
==

Linaro officially supports the current and previous Ubuntu LTS
releases (as of the time of this release).  This does not mean that
the toolchain will not work on other/older Linux distributions.  See
the following for the life-time of Ubuntu LTS releases.

https://wiki.ubuntu.com/Releases

The host system upon which the cross-compiler will run requires a
minimum of glibc 2.14, because of API changes to glibc's memcpy API.

https://bugs.linaro.org/show_bug.cgi?id=1869

Package Versions
=
Linaro GCC 4.9-2016.02

FSF eglibc 2.19 (eglibc.git/linaro_eglibc-2_19)

Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch)

Linaro binutils 2.24 (linaro_binutils-2_24-branch)

FSF GDB 7.10 (gdb-7.10-branch)

Linaro Linux Version 3.17-2014.10 (linux-linaro-3.17-2014.10)

Linaro toolchain package git branches are hosted at:

http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search

NEWS for Linaro GCC 4.9-2016.02


* The armv8l-linux-gnueabihf targetted toolchain is now built using
  --with-mode=thumb (like all of the other cross toolchains) rather than
  the default which is ARM mode.

* Applied fix for CVE-2015-7545 - A stack-based buffer overflow in
  glibc's getaddrinfo() was corrected in glibc 2.23 and backported into
  Linaro eglibc 2.19 (linaro_eglibc-2_19).

  https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html

* See the following Linaro GCC snapshot:

  http://snapshots.linaro.org/components/toolchain/gcc-linaro/4.9-2015.10/


Contact Linaro
===

File bugs at http://bugs.linaro.org

For Linaro member support see http://support.linaro.org

For Linaro community support email linaro-toolchain@lists.linaro.org

--

Ryan S. Arnold | Linaro Toolchain Engineering Manager
ryan.arn...@linaro.org | ryanarn on #linaro-tcwg @ freenode.irc.net
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 5.3-2016.05-rc2

[Ryan Arnold]

The Linaro Binary Toolchain


The Linaro GCC 5.3-2016.05-rc2 Release-Candidate is now available.

Notice: All Linaro GCC 5 series toolchain users should migrate to the
latest version of the Linaro GCC 5 toolchain in order to mitigate
potential security exposure to CVE-2015-7547.  See the NEWS section
below for details.

Download release-candidate packages from:


http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.05-rc2/

http://snapshots.linaro.org/components/toolchain/binaries/5.3-2016.05-rc2/

Previous snapshots and release-candidates are at:

http://snapshots.linaro.org/components/toolchain/binaries/

Previous releases are at:

http://releases.linaro.org/components/toolchain/binaries/

Host Requirements
==

Linaro officially supports the current and previous Ubuntu LTS
releases (as of the time of this release).  This does not mean that
the toolchain will not work on other/older Linux distributions.  See
the following for the life-time of Ubuntu LTS releases.

https://wiki.ubuntu.com/Releases

The host system upon which the cross-compiler will run requires a
minimum of glibc 2.14, because of API changes to glibc's memcpy API.

https://bugs.linaro.org/show_bug.cgi?id=1869

Package Versions
=
Linaro GCC 5.3-2016.05-rc2

Linaro glibc 2.21 (linaro/2.21)

Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch)

Linaro binutils 2.25 (linaro_binutils-2_25-branch)

FSF GDB 7.10 (gdb-7.10-branch)


Linaro toolchain package git branches are hosted at:

http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search

NEWS for Linaro GCC 5.3-2016.05-rc2

* Increment binutils release date to 2016_02 to reflect the most recent
  commit:

  commit ef90a4718f535cbe6345b4e7168baea7b1972abf
  Author: Matthew Wahab 
  Date:   Tue Jan 12 16:35:30 2016 +
  [ARM] Support ARMv8.2 RAS extension.

* Baremetal sysroot names now contain 'newlib' rather than 'glibc'.

* Manifests now contain relative paths rather than absolute paths.

* Now generating proper manifest files.

* Fixed pi requeue support in glibc 2.21 while allowing the existing
  2.21 minimum kernel default setting.  This was checked into the
  linaro/2.21/master branch.

  commit a68cafa11c500d8a49a3014c43c5152859d037ae
  Author: Adhemerval Zanella 
  Date:   Tue May 17 10:16:39 2016 -0300
  Add runtime check for __ASSUME_REQUEUE_PI (BZ# 18463)

  commit 6e5cb616b5b442ce8b2664ad673c0acf42a490ac
  Author: Adhemerval Zanella 
  Date:   Mon May 16 19:01:10 2016 -0300
  Remove __ASSUME_SET_ROBUST_LIST

  commit 9ac61c0047295696cbcdbc26bdc174c7bd25a3c8
  Author: Adhemerval Zanella 
  Date:   Mon May 16 10:35:25 2016 -0300
  Remove __ASSUME_FUTEX_LOCK_PI

* Backported support into GCC for Cortex-A32, Cortex-A35, and Cortex-R8.

* Applied fix for CVE-2015-7547 - A stack-based buffer overflow in
  glibc's getaddrinfo() was corrected in glibc 2.23 and backported into
  glibc 2.21.

  https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html

* ARMv8.1 Instruction Support - ARMv8.1 instructions support was checked
  into GCC and binutils.   It has been backported into Linaro GCC 5.3
  and Linaro binutils 2.25.

* Backported -Bsymbolic-functions into Linaro binutils 2.25.

* Performance related backports from Linaro GCC 5.2-2015.11, Linaro GCC
  5.2-2015.12, and Linaro GCC 5.3-2016.01-1, Linaro GCC 5.3-2016.02,
  Linaro GCC 5.3-2016.03, and Linaro GCC 5.3-2016.04 have been included.

  See the following Linaro GCC snapshots:

  http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.2-2015.11/
  http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2015.12/
  http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.01-1/
  http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.02
  http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.03
  http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.04


Contact Linaro
===

File bugs at http://bugs.linaro.org

For Linaro member support see http://support.linaro.org

For Linaro community support email linaro-toolchain@lists.linaro.org

-- 

Ryan S. Arnold | Linaro Toolchain Engineering Manager

ryan.arn...@linaro.org | ryanarn on #linaro-tcwg @ freenode.irc.net
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ANNOUNCE] Linaro Binary Toolchain Release GCC 5.3-2016.05

[Ryan Arnold]

The Linaro Binary Toolchain


The Linaro GCC 5.3-2016.05 Release is now available.

Notice: All Linaro GCC 5 series toolchain users should migrate to the
latest version of the Linaro GCC 5 toolchain in order to mitigate
potential security exposure to CVE-2015-7547.  See the NEWS section
below for details.

Download release packages from:


http://releases.linaro.org/components/toolchain/gcc-linaro/5.3-2016.05/

http://releases.linaro.org/components/toolchain/binaries/5.3-2016.05/

Previous snapshots and release-candidates are at:

http://snapshots.linaro.org/components/toolchain/binaries/

Previous releases are at:

http://releases.linaro.org/components/toolchain/binaries/

Host Requirements
==

Linaro officially supports the current and previous Ubuntu LTS
releases (as of the time of this release).  This does not mean that
the toolchain will not work on other/older Linux distributions.  See
the following for the life-time of Ubuntu LTS releases.

https://wiki.ubuntu.com/Releases

The host system upon which the cross-compiler will run requires a
minimum of glibc 2.14, because of API changes to glibc's memcpy API.

https://bugs.linaro.org/show_bug.cgi?id=1869

Package Versions
=
Linaro GCC 5.3-2016.05

Linaro glibc 2.21 (linaro/2.21)

Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch)

Linaro binutils 2.25 (linaro_binutils-2_25-branch)

FSF GDB 7.10 (gdb-7.10-branch)


Linaro toolchain package git branches are hosted at:

http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search

NEWS for Linaro GCC 5.3-2016.05

* Increment binutils release date to 2016_02 to reflect the most recent
  commit:

  commit ef90a4718f535cbe6345b4e7168baea7b1972abf
  Author: Matthew Wahab 
  Date:   Tue Jan 12 16:35:30 2016 +
  [ARM] Support ARMv8.2 RAS extension.

* Baremetal sysroot names now contain 'newlib' rather than 'glibc'.

* Manifests now contain relative paths rather than absolute paths.

* Now generating proper manifest files.

* Fixed pi requeue support in glibc 2.21 while allowing the existing
  2.21 minimum kernel default setting.  This was checked into the
  linaro/2.21/master branch.

  commit a68cafa11c500d8a49a3014c43c5152859d037ae
  Author: Adhemerval Zanella 
  Date:   Tue May 17 10:16:39 2016 -0300
  Add runtime check for __ASSUME_REQUEUE_PI (BZ# 18463)

  commit 6e5cb616b5b442ce8b2664ad673c0acf42a490ac
  Author: Adhemerval Zanella 
  Date:   Mon May 16 19:01:10 2016 -0300
  Remove __ASSUME_SET_ROBUST_LIST

  commit 9ac61c0047295696cbcdbc26bdc174c7bd25a3c8
  Author: Adhemerval Zanella 
  Date:   Mon May 16 10:35:25 2016 -0300
  Remove __ASSUME_FUTEX_LOCK_PI

* Backported support into GCC for Cortex-A32, Cortex-A35, and Cortex-R8.

* Applied fix for CVE-2015-7547 - A stack-based buffer overflow in
  glibc's getaddrinfo() was corrected in glibc 2.23 and backported into
  glibc 2.21.

  https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html

* ARMv8.1 Instruction Support - ARMv8.1 instructions support was checked
  into GCC and binutils.   It has been backported into Linaro GCC 5.3
  and Linaro binutils 2.25.

* Backported -Bsymbolic-functions into Linaro binutils 2.25.

* Performance related backports from Linaro GCC 5.2-2015.11, Linaro GCC
  5.2-2015.12, and Linaro GCC 5.3-2016.01-1, Linaro GCC 5.3-2016.02,
  Linaro GCC 5.3-2016.03, and Linaro GCC 5.3-2016.04 have been included.

  See the following Linaro GCC snapshots:


http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.2-2015.11/

http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2015.12/

http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.01-1/

http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.02

http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.03

http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.04


Contact Linaro
===

File bugs at http://bugs.linaro.org

For Linaro member support see http://support.linaro.org

For Linaro community support email linaro-toolchain@lists.linaro.org

-- 

Ryan S. Arnold | Linaro Toolchain Engineering Manager

ryan.arn...@linaro.org | ryanarn on #linaro-tcwg @ freenode.irc.net

T: +1-612-424-1861 <+16124241861>
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 6.1-2016.08-rc1

[Ryan Arnold]

The Linaro Binary Toolchain


The Linaro GCC 6.1-2016.08-rc1 Release-Candidate is now available.

Download release-candidate packages from:


http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.1-2016.08-rc1/

http://snapshots.linaro.org/components/toolchain/binaries/6.1-2016.08-rc1/

Previous snapshots and release-candidates are at:

http://snapshots.linaro.org/components/toolchain/binaries/

Previous releases are at:

http://releases.linaro.org/components/toolchain/binaries/

Host Requirements
==

Linaro officially supports the current and previous Ubuntu LTS
releases (as of the time of this release).  This does not mean that
the toolchain will not work on other/older Linux distributions.  See
the following for the life-time of Ubuntu LTS releases.

https://wiki.ubuntu.com/Releases

The host system upon which the cross-compiler will run requires a
minimum of glibc 2.14, because of API changes to glibc's memcpy API.

https://bugs.linaro.org/show_bug.cgi?id=1869

Package Versions
=
Linaro GCC 6.1-2016.08-rc1

FSF glibc 2.23 (linaro/2.23)

Linaro newlib 2.4.0-2016.03 (linaro-2.4-branch)

Linaro binutils 2.26 (linaro_binutils-2_26-branch)

FSF GDB 7.11 (binutils-gdb.git~gdb-7.11-branch)


Linaro toolchain package git branches are hosted at:

http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search

NEWS for Linaro GCC 6.1-2016.08-rc1


* Performance related backports from Linaro GCC 6.1-2016.06, and Linaro
  GCC 6.1-2016.07 have been included.

  See the following Linaro GCC snapshots:

  http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.1-2016.06/
  http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.1-2016.07/


Contact Linaro
===

File bugs at http://bugs.linaro.org

For Linaro member support see http://support.linaro.org

For Linaro community support email linaro-toolchain@lists.linaro.org

-- 

Ryan S. Arnold | Linaro Toolchain Engineering Manager
ryan.arn...@linaro.org | ryanarn on #linaro-tcwg @ freenode.irc.net
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 6.1-2016.08-rc2

[Ryan Arnold]

The Linaro Binary Toolchain


The Linaro GCC 6.1-2016.08-rc2 Release-Candidate is now available.

The GCC 6 Release series has significant changes from the GCC 5
release series.  For an explanation of the changes please see the
following website:

https://gcc.gnu.org/gcc-6/changes.html
For help in porting to GCC 6 please see the following explanation:

https://gcc.gnu.org/gcc-6/porting_to.html

Download release-candidate packages from:


http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.1-2016.08-rc2/

http://snapshots.linaro.org/components/toolchain/binaries/6.1-2016.08-rc2/

Previous snapshots and release-candidates are at:

http://snapshots.linaro.org/components/toolchain/binaries/

Previous releases are at:

http://releases.linaro.org/components/toolchain/binaries/

Host Requirements
==

Linaro officially supports the current and previous Ubuntu LTS
releases (as of the time of this release).  This does not mean that
the toolchain will not work on other/older Linux distributions.  See
the following for the life-time of Ubuntu LTS releases.

https://wiki.ubuntu.com/Releases

The host system upon which the cross-compiler will run requires a
minimum of glibc 2.14, because of API changes to glibc's memcpy API.

https://bugs.linaro.org/show_bug.cgi?id=1869

Package Versions
=
Linaro GCC 6.1-2016.08-rc2


http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.1-2016.08-rc2/

FSF glibc 2.23 (linaro/2.23)

https://www.sourceware.org/ml/libc-alpha/2016-08/msg00212.html

Linaro newlib 2.4.0-2016.03 (linaro-2.4-branch)

Linaro binutils 2.27 (linaro_binutils-2_27-branch)


https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=binutils/NEWS;hb=refs/tags/binutils-2_27

FSF GDB 7.11 (binutils-gdb.git~gdb-7.11-branch)

https://lists.gnu.org/archive/html/info-gnu/2016-02/msg00010.html

Linaro toolchain package git branches are hosted at:

http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search

NEWS for Linaro GCC 6.1-2016.08-rc2


* Copy the libwinpthread DLL into the bin directories so it gets into
  the tmp directory before tar is run.

  https://review.linaro.org/#/c/13723/

* Include GNU Assembler fix for PR 20364

  commit 5fe7ebe5ab43750abf8f490b785d99a1e598e7fd
  Author: Nick Clifton 
  Date:   Fri Aug 5 10:37:57 2016 +0100
  Fix the generation of alignment frags in code sections for AArch64.

  https://sourceware.org/bugzilla/show_bug.cgi?id=20364

* Performance related backports from Linaro GCC 6.1-2016.06, and Linaro
  GCC 6.1-2016.07 have been included.

  See the following Linaro GCC snapshots:

  http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.1-2016.06/
  http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.1-2016.07/


Contact Linaro
===

File bugs at http://bugs.linaro.org

For Linaro member support see http://support.linaro.org

For Linaro community support email linaro-toolchain@lists.linaro.org

-- 
Ryan S. Arnold | Linaro Toolchain Engineering Manager
ryan.arn...@linaro.org | ryanarn on #linaro-tcwg @ freenode.irc.net
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ANNOUNCE] Linaro Binary Toolchain Release GCC 6.1-2016.08

[Ryan Arnold]

The Linaro Binary Toolchain


The Linaro GCC 6.1-2016.08 Release is now available.

The GCC 6 Release series has significant changes from the GCC 5
release series.  For an explanation of the changes please see the
following website:

https://gcc.gnu.org/gcc-6/changes.html

For help in porting to GCC 6 please see the following explanation:

https://gcc.gnu.org/gcc-6/porting_to.html

Download release packages from:

http://releases.linaro.org/components/toolchain/gcc-linaro/6.1-2016.08/
http://releases.linaro.org/components/toolchain/binaries/6.1-2016.08/

Previous snapshots and release-candidates are at:

http://snapshots.linaro.org/components/toolchain/binaries/

Previous releases are at:

http://releases.linaro.org/components/toolchain/binaries/

Host Requirements
==

Linaro officially supports the current and previous Ubuntu LTS
releases (as of the time of this release).  This does not mean that
the toolchain will not work on other/older Linux distributions.  See
the following for the life-time of Ubuntu LTS releases.

https://wiki.ubuntu.com/Releases

The host system upon which the cross-compiler will run requires a
minimum of glibc 2.14, because of API changes to glibc's memcpy API.

https://bugs.linaro.org/show_bug.cgi?id=1869

Package Versions
=
Linaro GCC 6.1-2016.08

http://releases.linaro.org/components/toolchain/gcc-linaro/6.1-2016.08/

FSF glibc 2.23 (linaro/2.23)

https://www.sourceware.org/ml/libc-alpha/2016-08/msg00212.html

Linaro newlib 2.4.0-2016.03 (linaro-2.4-branch)

Linaro binutils 2.27 (linaro_binutils-2_27-branch)


https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=binutils/NEWS;hb=refs/tags/binutils-2_27

FSF GDB 7.11 (binutils-gdb.git~gdb-7.11-branch)

https://lists.gnu.org/archive/html/info-gnu/2016-02/msg00010.html

Linaro toolchain package git branches are hosted at:

http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search

NEWS for Linaro GCC 6.1-2016.08


* Include GNU Linker fix.

  commit fbc6c6763e70cb2376e2de990c7fc54c0ee44a59
  Author: Nick Clifton 
  Date:   Tue Aug 23 09:45:11 2016 +0100
  Fix seg-fault in ARM linker when trying to parse a binary file.

* Copy the libwinpthread DLL into the bin directories so it gets into
  the tmp directory before tar is run.

  https://review.linaro.org/#/c/13723/

* Include GNU Assembler fix for PR 20364

  commit 5fe7ebe5ab43750abf8f490b785d99a1e598e7fd
  Author: Nick Clifton 
  Date:   Fri Aug 5 10:37:57 2016 +0100
  Fix the generation of alignment frags in code sections for AArch64.

  https://sourceware.org/bugzilla/show_bug.cgi?id=20364

* Performance related backports from Linaro GCC 6.1-2016.06, and Linaro
  GCC 6.1-2016.07 have been included.

  See the following Linaro GCC snapshots:

  http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.1-2016.06/
  http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.1-2016.07/


Contact Linaro
===

File bugs at http://bugs.linaro.org

For Linaro member support see http://support.linaro.org

For Linaro community support email linaro-toolchain@lists.linaro.org

-- 
Ryan S. Arnold | Linaro Toolchain Engineering Manager
ryan.arn...@linaro.org | ryanarn on #linaro-tcwg @ freenode.irc.net
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 6.2-2016.11-rc1

[Ryan Arnold]

The Linaro Binary Toolchain


The Linaro GCC 6.2-2016.11-rc1 Release-Candidate is now available.

The GCC 6 Release series has significant changes from the GCC 5
release series.  For an explanation of the changes please see the
following website:

https://gcc.gnu.org/gcc-6/changes.html

For help in porting to GCC 6 please see the following explanation:

https://gcc.gnu.org/gcc-6/porting_to.html

Download release-candidate packages from:


http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.2-2016.11-rc1/

http://snapshots.linaro.org/components/toolchain/binaries/6.2-2016.11-rc1/

Previous snapshots and release-candidates are at:

http://snapshots.linaro.org/components/toolchain/binaries/

Previous releases are at:

http://releases.linaro.org/components/toolchain/binaries/

Host Requirements
==

Linaro officially supports the current and previous Ubuntu LTS
releases (as of the time of this release).  This does not mean that
the toolchain will not work on other/older Linux distributions.  See
the following for the life-time of Ubuntu LTS releases.

https://wiki.ubuntu.com/Releases

The host system upon which the cross-compiler will run requires a
minimum of glibc 2.14, because of API changes to glibc's memcpy API.

https://bugs.linaro.org/show_bug.cgi?id=1869

Package Versions
=
Linaro GCC 6.2-2016.11-rc1

Linaro glibc 2.23 (linaro/2.23/master)

https://www.sourceware.org/ml/libc-alpha/2016-08/msg00212.html

Linaro newlib 2.4-2016.03 (linaro_2.4-branch)

Linaro binutils 2.27 (linaro_binutils-2_27-branch)


https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=binutils/NEWS;hb=refs/tags/binutils-2_27

Linaro GDB 7.12 (gdb-7.12-branch)

https://sourceware.org/ml/gdb/2016-08/msg0.html


Linaro toolchain package git branches are hosted at:

http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search

NEWS for Linaro GCC 6.2-2016.11-rc1


* The Linaro GCC 6.2-2016.10 snapshot added AArch32 support for ARMv8.2
  and ARMv8m, as well as some AArch64 fixes for ARMv8.2, and bug fixes
  merged from FSF GCC 6.2.

* Basic tuning support for the Qualcomm qdf24xx was added to the Linaro
  GCC 6.2-2016.10 snapshot and will appear in this release.

* IFUNC was disabled for baremetal targets, as it was causing test-suite
  failures, and is presently a Linux only feature.

* The gold linker was also added to this binary releases (for linux
  targets).

* Backported malloc_lock fix into Linaro newlib 2.4.

  commit 022bd2995640626d9efb6a839884c5e1c7c5e133
  Author: Christophe Lyon 
  Date:   Wed Oct 19 14:11:50 2016 +0200
  Re-enable malloc_lock for newlib-nano

* Backported rawmemchr patch into Linaro newlib 2.4.

  commit 5357441171f2409fb759112bc6a00d3e672374d9
  Author: Christophe Lyon 
  Date:   Wed Oct 19 14:09:51 2016 +0200
  Add rawmemchr

* Backported strlen fix when using Thumb-2 and -Os -marm into Linaro
  newlib 2.4.

  commit f194ff4d5e1e304ac2a8d438d7abcbffd2dba757
  Author: Christophe Lyon 
  Date:   Wed Oct 19 14:05:23 2016 +0200
  Fix strlen using Thumb-2 with -Os -marm

* Backported fix for semihosting ARM when heapinfo not provided by
  debugger into Linaro newlib 2.4.

  commit bda499cb9d2b97075f74df9bfb38b23ff4d12ac2
  Author: Christophe Lyon 
  Date:   Wed Oct 19 13:59:52 2016 +0200
  Fixed semihosting for ARM when heapinfo not provided by debugger.

* Merged latest FSF glibc release/2.23/master into Linaro glibc 2.23.

* Added __ASSUME_REQUEUE_PI support to Linaro glibc 2.23 branch.

  commit 2d20c3bf918cd94ebd4106693adb3a5c9272baba
  Author: Adhemerval Zanella 
  Date:   Tue May 17 10:16:39 2016 -0300
  Add runtime check for __ASSUME_REQUEUE_PI (BZ# 18463)

* Added __ASSUME_SET_ROBUST_LIST support to Linaro glibc 2.23 branch.

  commit bb8f09d72756186a3d82a1f7b2adcf8bc1fbaed1
  Author: Adhemerval Zanella 
  Date:   Mon May 16 19:01:10 2016 -0300
  Remove __ASSUME_SET_ROBUST_LIST

* Added __ASSUME_FUTEX_LOCK_PI support to Linaro glibc 2.23 branch.

  commit e48b4e7fed0de06dd7832ead48bea8ebc813a204
  Author: Adhemerval Zanella 
  Date:   Mon May 16 10:35:25 2016 -0300
  Remove __ASSUME_FUTEX_LOCK_PI

* Merged latest FSF binutils-2_27-branch into
  linaro_binutils-2_27-branch.

* Include GNU Linker fix.

  commit fbc6c6763e70cb2376e2de990c7fc54c0ee44a59
  Author: Nick Clifton 
  Date:   Tue Aug 23 09:45:11 2016 +0100
  Fix seg-fault in ARM linker when trying to parse a binary file.

* Copy the libwinpthread DLL into the bin directories so it gets into
  the tmp directory before tar is run.

  https://review.linaro.org/#/c/13723/

* Include GNU Assembler fix for PR 20364

  commit 5fe7ebe5ab43750abf8f490b785d99a1e598e7fd
  Author: Nick Clifton 
  Date:   Fri Aug 5 10:37:57 2016 +0100
  Fix the generation of alignment frags in code sections for AArch64.

  https://sourceware.o

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 6.2-2016.11-rc2

[Ryan Arnold]

The Linaro Binary Toolchain


The Linaro GCC 6.2-2016.11-rc2 Release-Candidate is now available.

The GCC 6 Release series has significant changes from the GCC 5
release series.  For an explanation of the changes please see the
following website:

https://gcc.gnu.org/gcc-6/changes.html

For help in porting to GCC 6 please see the following explanation:

https://gcc.gnu.org/gcc-6/porting_to.html

Download release-candidate packages from:


http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.2-2016.11-rc2/

http://snapshots.linaro.org/components/toolchain/binaries/6.2-2016.11-rc2/

Previous snapshots and release-candidates are at:

http://snapshots.linaro.org/components/toolchain/binaries/

Previous releases are at:

http://releases.linaro.org/components/toolchain/binaries/

Host Requirements
==

Linaro officially supports the current and previous Ubuntu LTS
releases (as of the time of this release).  This does not mean that
the toolchain will not work on other/older Linux distributions.  See
the following for the life-time of Ubuntu LTS releases.

https://wiki.ubuntu.com/Releases

The host system upon which the cross-compiler will run requires a
minimum of glibc 2.14, because of API changes to glibc's memcpy API.

https://bugs.linaro.org/show_bug.cgi?id=1869

Package Versions
=
Linaro GCC 6.2-2016.11-rc2

Linaro glibc 2.23 (linaro/2.23/master)

https://www.sourceware.org/ml/libc-alpha/2016-08/msg00212.html

Linaro newlib 2.4-2016.03 (linaro_2.4-branch)

Linaro binutils 2.27 (linaro_binutils-2_27-branch)


https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=binutils/NEWS;hb=refs/tags/binutils-2_27

Linaro GDB 7.12 (gdb-7.12-branch)

https://lists.gnu.org/archive/html/info-gnu/2016-10/msg7.html


Linaro toolchain package git branches are hosted at:

http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search

NEWS for Linaro GCC 6.2-2016.11-rc2


* Host binaries for x86_64 linux hosts now have symbols and debug
  information stripped in order to reduce the size of the toolchain
  binary archives.  This reduces the archive size from 1.5G to 600M for
  aarch64-linux-gnu target with the gcc-6-branch.

  https://review.linaro.org/#/c/15504/

* Removed GCC patch for revision 239561 as it was causing an upstream
  regression

  commit 03850689f4c165e88cec81696d9d722e76a86c85
  Author: Yvan Roux 
  Date:   Wed Nov 9 21:56:21 2016 +0100
  Revert backport from trunk r239561.
  This reverts commit 11879870dc041028bcb8d078d9ddbd7e400dd03f.

* Updated GDB from GDB 7.11 to GDB 7.12.

* The Linaro GCC 6.2-2016.10 snapshot added AArch32 support for ARMv8.2
  and ARMv8m, as well as some AArch64 fixes for ARMv8.2, and bug fixes
  merged from FSF GCC 6.2.

* Basic tuning support for the Qualcomm qdf24xx was added to the Linaro
  GCC 6.2-2016.10 snapshot and will appear in this release.

* IFUNC was disabled for baremetal targets, as it was causing test-suite
  failures, and is presently a Linux only feature.

* The gold linker was added to this binary release.

* Backported malloc_lock fix into Linaro newlib 2.4.

  commit 022bd2995640626d9efb6a839884c5e1c7c5e133
  Author: Christophe Lyon 
  Date:   Wed Oct 19 14:11:50 2016 +0200
  Re-enable malloc_lock for newlib-nano

* Backported rawmemchr patch into Linaro newlib 2.4.

  commit 5357441171f2409fb759112bc6a00d3e672374d9
  Author: Christophe Lyon 
  Date:   Wed Oct 19 14:09:51 2016 +0200
  Add rawmemchr

* Backported strlen fix when using Thumb-2 and -Os -marm into Linaro
  newlib 2.4.

  commit f194ff4d5e1e304ac2a8d438d7abcbffd2dba757
  Author: Christophe Lyon 
  Date:   Wed Oct 19 14:05:23 2016 +0200
  Fix strlen using Thumb-2 with -Os -marm

* Backported fix for semihosting ARM when heapinfo not provided by
  debugger into Linaro newlib 2.4.

  commit bda499cb9d2b97075f74df9bfb38b23ff4d12ac2
  Author: Christophe Lyon 
  Date:   Wed Oct 19 13:59:52 2016 +0200
  Fixed semihosting for ARM when heapinfo not provided by debugger.

* Merged latest FSF glibc release/2.23/master into Linaro glibc 2.23.

* Backported __ASSUME_REQUEUE_PI check Linaro glibc 2.23 branch.

  commit 2d20c3bf918cd94ebd4106693adb3a5c9272baba
  Author: Adhemerval Zanella 
  Date:   Tue May 17 10:16:39 2016 -0300
  Add runtime check for __ASSUME_REQUEUE_PI (BZ# 18463)

* Backported removal of __ASSUME_SET_ROBUST_LIST from Linaro glibc 2.23
  branch.

  commit bb8f09d72756186a3d82a1f7b2adcf8bc1fbaed1
  Author: Adhemerval Zanella 
  Date:   Mon May 16 19:01:10 2016 -0300
  Remove __ASSUME_SET_ROBUST_LIST

* Backported removal of __ASSUME_FUTEX_LOCK_PI from Linaro glibc 2.23
  branch.

  commit e48b4e7fed0de06dd7832ead48bea8ebc813a204
  Author: Adhemerval Zanella 
  Date:   Mon May 16 10:35:25 2016 -0300
  Remove __ASSUME_FUTEX_LOCK_PI

* Merged latest FSF binutils-2_27-branch in

[ANNOUNCE] Linaro Binary Toolchain Release GCC 6.2-2016.11

[Ryan Arnold]

The Linaro Binary Toolchain


The Linaro GCC 6.2-2016.11 Release is now available.

The GCC 6 Release series has significant changes from the GCC 5
release series.  For an explanation of the changes please see the
following website:

https://gcc.gnu.org/gcc-6/changes.html

For help in porting to GCC 6 please see the following explanation:

https://gcc.gnu.org/gcc-6/porting_to.html

Download release packages from:

http://releases.linaro.org/components/toolchain/gcc-linaro/6.2-2016.11/
http://releases.linaro.org/components/toolchain/binaries/6.2-2016.11/

Previous snapshots and release-candidates are at:

http://snapshots.linaro.org/components/toolchain/binaries/

Previous releases are at:

http://releases.linaro.org/components/toolchain/binaries/

Host Requirements
==

Linaro officially supports the current and previous Ubuntu LTS
releases (as of the time of this release).  This does not mean that
the toolchain will not work on other/older Linux distributions.  See
the following for the life-time of Ubuntu LTS releases.

https://wiki.ubuntu.com/Releases

The host system upon which the cross-compiler will run requires a
minimum of glibc 2.14, because of API changes to glibc's memcpy API.

https://bugs.linaro.org/show_bug.cgi?id=1869

Package Versions
=
Linaro GCC 6.2-2016.11

Linaro glibc 2.23 (linaro/2.23/master)

https://www.sourceware.org/ml/libc-alpha/2016-08/msg00212.html

Linaro newlib 2.4-2016.03 (linaro_2.4-branch)

Linaro binutils 2.27 (linaro_binutils-2_27-branch)


https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=binutils/NEWS;hb=refs/tags/binutils-2_27

Linaro GDB 7.12 (gdb-7.12-branch)

https://lists.gnu.org/archive/html/info-gnu/2016-10/msg7.html


Linaro toolchain package git branches are hosted at:

http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search

NEWS for Linaro GCC 6.2-2016.11


* Host binaries for x86_64 linux hosts now have symbols and debug
  information stripped in order to reduce the size of the toolchain
  binary archives.  This reduces the archive size from 1.5G to 600M for
  aarch64-linux-gnu target with the gcc-6-branch.

* Removed GCC patch for revision 239561 as it was causing an upstream
  regression

  commit 03850689f4c165e88cec81696d9d722e76a86c85
  Author: Yvan Roux 
  Date:   Wed Nov 9 21:56:21 2016 +0100
  Revert backport from trunk r239561.
  This reverts commit 11879870dc041028bcb8d078d9ddbd7e400dd03f.

* The GDB version was upgraded from GDB 7.11 in the 6.1-2016.08 release
  to GDB 7.12 in 6.2-2016.11.

* The Linaro GCC 6.2-2016.10 snapshot added AArch32 support for ARMv8.2
  and ARMv8m, as well as some AArch64 fixes for ARMv8.2, and bug fixes
  merged from FSF GCC 6.2.

* Basic tuning support for the Qualcomm qdf24xx was added to the Linaro
  GCC 6.2-2016.10 snapshot and will appear in this release.

* IFUNC was disabled for baremetal targets, as it was causing test-suite
  failures, and is presently a Linux only feature.

* The gold linker was added to this binary release.

* Backported malloc_lock fix into Linaro newlib 2.4.

  commit 022bd2995640626d9efb6a839884c5e1c7c5e133
  Author: Christophe Lyon 
  Date:   Wed Oct 19 14:11:50 2016 +0200
  Re-enable malloc_lock for newlib-nano

* Backported rawmemchr patch into Linaro newlib 2.4.

  commit 5357441171f2409fb759112bc6a00d3e672374d9
  Author: Christophe Lyon 
  Date:   Wed Oct 19 14:09:51 2016 +0200
  Add rawmemchr

* Backported strlen fix when using Thumb-2 and -Os -marm into Linaro
  newlib 2.4.

  commit f194ff4d5e1e304ac2a8d438d7abcbffd2dba757
  Author: Christophe Lyon 
  Date:   Wed Oct 19 14:05:23 2016 +0200
  Fix strlen using Thumb-2 with -Os -marm

* Backported fix for semihosting ARM when heapinfo not provided by
  debugger into Linaro newlib 2.4.

  commit bda499cb9d2b97075f74df9bfb38b23ff4d12ac2
  Author: Christophe Lyon 
  Date:   Wed Oct 19 13:59:52 2016 +0200
  Fixed semihosting for ARM when heapinfo not provided by debugger.

* Merged latest FSF glibc release/2.23/master into Linaro glibc 2.23.

* Backported __ASSUME_REQUEUE_PI check Linaro glibc 2.23 branch.

  commit 2d20c3bf918cd94ebd4106693adb3a5c9272baba
  Author: Adhemerval Zanella 
  Date:   Tue May 17 10:16:39 2016 -0300
  Add runtime check for __ASSUME_REQUEUE_PI (BZ# 18463)

* Backported removal of __ASSUME_SET_ROBUST_LIST from Linaro glibc 2.23
  branch.

  commit bb8f09d72756186a3d82a1f7b2adcf8bc1fbaed1
  Author: Adhemerval Zanella 
  Date:   Mon May 16 19:01:10 2016 -0300
  Remove __ASSUME_SET_ROBUST_LIST

* Backported removal of __ASSUME_FUTEX_LOCK_PI from Linaro glibc 2.23
  branch.

  commit e48b4e7fed0de06dd7832ead48bea8ebc813a204
  Author: Adhemerval Zanella 
  Date:   Mon May 16 10:35:25 2016 -0300
  Remove __ASSUME_FUTEX_LOCK_PI

* Merged latest FSF binutils-2_27-branch into
  linaro_binutils-2_27-branc

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 5.4-2017.01-rc1

[Ryan Arnold]

The Linaro Binary Toolchain


The Linaro GCC 5.4-2017.01-rc1 Release-Candidate is now available.

Notice: All Linaro GCC 5 series toolchain users should migrate to the
latest version of the Linaro GCC 5 toolchain in order to mitigate
potential security exposure to CVE-2015-7547.  See the NEWS section
below for details.

Download release-candidate packages from:


http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.4-2017.01-rc1/

http://snapshots.linaro.org/components/toolchain/binaries/5.4-2017.01-rc1/

Previous snapshots and release-candidates are at:

http://snapshots.linaro.org/components/toolchain/binaries/

Previous releases are at:

http://releases.linaro.org/components/toolchain/binaries/

Host Requirements
==

Linaro officially supports the current and previous Ubuntu LTS
releases (as of the time of this release).  This does not mean that
the toolchain will not work on other/older Linux distributions.  See
the following for the life-time of Ubuntu LTS releases.

https://wiki.ubuntu.com/Releases

The host system upon which the cross-compiler will run requires a
minimum of glibc 2.14, because of API changes to glibc's memcpy API.

https://bugs.linaro.org/show_bug.cgi?id=1869

Package Versions
=
Linaro GCC 5.4-2017.01-rc1

Linaro glibc 2.21 (linaro/2.21)

Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch)

Linaro binutils 2.25 (linaro_binutils-2_25-branch)

FSF GDB 7.12 (gdb-7.12-branch)


Linaro toolchain package git branches are hosted at:

http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search

NEWS for Linaro GCC 5.4-2017.01-rc1

* Include GCC fix for Linaro bugzilla #1925:

  [regression] FAIL: libgomp.fortran/retval1.f90 -O1 execution test

  https://bugs.linaro.org/show_bug.cgi?id=1925

* Include GCC fix for Linaro bugzilla #2185:

  aarch64-linux-gnu-g++ internal compiler error: in curr_insn_transform

  https://bugs.linaro.org/show_bug.cgi?id=2185

* Copy the libwinpthread DLL into the bin directories so it gets into
  the tmp directory before tar is run.

  https://review.linaro.org/#/c/13723/

* Increment binutils release date to 2016_02 to reflect the most recent
  commit:

  commit ef90a4718f535cbe6345b4e7168baea7b1972abf
  Author: Matthew Wahab 
  Date:   Tue Jan 12 16:35:30 2016 +
  [ARM] Support ARMv8.2 RAS extension.

* Baremetal sysroot names now contain 'newlib' rather than 'glibc'.

* Manifests now contain relative paths rather than absolute paths.

* Now generating proper manifest files.

* Fixed pi requeue support in glibc 2.21 while allowing the existing
  2.21 minimum kernel default setting.  This was checked into the
  linaro/2.21/master branch.

  commit a68cafa11c500d8a49a3014c43c5152859d037ae
  Author: Adhemerval Zanella 
  Date:   Tue May 17 10:16:39 2016 -0300
  Add runtime check for __ASSUME_REQUEUE_PI (BZ# 18463)

  commit 6e5cb616b5b442ce8b2664ad673c0acf42a490ac
  Author: Adhemerval Zanella 
  Date:   Mon May 16 19:01:10 2016 -0300
  Remove __ASSUME_SET_ROBUST_LIST

  commit 9ac61c0047295696cbcdbc26bdc174c7bd25a3c8
  Author: Adhemerval Zanella 
  Date:   Mon May 16 10:35:25 2016 -0300
  Remove __ASSUME_FUTEX_LOCK_PI

* Backported support into GCC for Cortex-A32, Cortex-A35, and Cortex-R8.

* Applied fix for CVE-2015-7547 - A stack-based buffer overflow in
  glibc's getaddrinfo() was corrected in glibc 2.23 and backported into
  glibc 2.21.

  https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html

* ARMv8.1 Instruction Support - ARMv8.1 instructions support was checked
  into GCC and binutils.   It has been backported into Linaro GCC 5.3
  and Linaro binutils 2.25.

* Backported -Bsymbolic-functions into Linaro binutils 2.25.

* Performance related backports from Linaro GCC 5.2-2015.11, Linaro GCC
  5.2-2015.12, and Linaro GCC 5.3-2016.01-1, Linaro GCC 5.3-2016.02,
  Linaro GCC 5.3-2016.03, Linaro GCC 5.3-2016.04, Linaro GCC
  5.4-2016.06, Linaro GCC 5.4-2016.10 and Linaro GCC 5.4-2016.12 have
  been included.

  See the following Linaro GCC snapshots:

  http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.2-2015.11/
  http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2015.12/
  http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.01-1/
  http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.02
  http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.03
  http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.04
  http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.4-2016.06
  http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.4-2016.10
  http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.4-2016.12


Contact Linaro
===

File bugs at http://bugs.linaro.org

For Linaro member support see http://support.linaro.org

For

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 5.4-2017.01-rc2

[Ryan Arnold]

The Linaro Binary Toolchain


The Linaro GCC 5.4-2017.01-rc2 Release-Candidate is now available.

Notice: All Linaro GCC 5 series toolchain users should migrate to the
latest version of the Linaro GCC 5 toolchain in order to mitigate
potential security exposure to CVE-2015-7547.  See the NEWS section
below for details.

Download release-candidate packages from:


http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.4-2017.01-rc2/

http://snapshots.linaro.org/components/toolchain/binaries/5.4-2017.01-rc2/

Previous snapshots and release-candidates are at:

http://snapshots.linaro.org/components/toolchain/binaries/

Previous releases are at:

http://releases.linaro.org/components/toolchain/binaries/

Host Requirements
==

Linaro officially supports the current and previous Ubuntu LTS
releases (as of the time of this release).  This does not mean that
the toolchain will not work on other/older Linux distributions.  See
the following for the life-time of Ubuntu LTS releases.

https://wiki.ubuntu.com/Releases

The host system upon which the cross-compiler will run requires a
minimum of glibc 2.14, because of API changes to glibc's memcpy API.

https://bugs.linaro.org/show_bug.cgi?id=1869

Package Versions
=
Linaro GCC 5.4-2017.01-rc2

Linaro glibc 2.21 (linaro/2.21)

Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch)

Linaro binutils 2.25 (linaro_binutils-2_25-branch)

FSF GDB 7.12 (gdb-7.12-branch)


Linaro toolchain package git branches are hosted at:

http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search

NEWS for Linaro GCC 5.4-2017.01-rc2

* Include GCC fix for upstream bugzilla PR target/78253:

  [5/6/7 Regression] [ARM] call weak function instead of strong when
  called through pointer

  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78253

* Include GCC fix for Linaro bugzilla #1925:

  [regression] FAIL: libgomp.fortran/retval1.f90 -O1 execution test

  https://bugs.linaro.org/show_bug.cgi?id=1925

* Include GCC fix for Linaro bugzilla #2185:

  aarch64-linux-gnu-g++ internal compiler error: in curr_insn_transform

  https://bugs.linaro.org/show_bug.cgi?id=2185

* Copy the libwinpthread DLL into the bin directories so it gets into
  the tmp directory before tar is run.

  https://review.linaro.org/#/c/13723/

* Increment binutils release date to 2016_02 to reflect the most recent
  commit:

  commit ef90a4718f535cbe6345b4e7168baea7b1972abf
  Author: Matthew Wahab 
  Date:   Tue Jan 12 16:35:30 2016 +
  [ARM] Support ARMv8.2 RAS extension.

* Baremetal sysroot names now contain 'newlib' rather than 'glibc'.

* Manifests now contain relative paths rather than absolute paths.

* Now generating proper manifest files.

* Fixed pi requeue support in glibc 2.21 while allowing the existing
  2.21 minimum kernel default setting.  This was checked into the
  linaro/2.21/master branch.

  commit a68cafa11c500d8a49a3014c43c5152859d037ae
  Author: Adhemerval Zanella 
  Date:   Tue May 17 10:16:39 2016 -0300
  Add runtime check for __ASSUME_REQUEUE_PI (BZ# 18463)

  commit 6e5cb616b5b442ce8b2664ad673c0acf42a490ac
  Author: Adhemerval Zanella 
  Date:   Mon May 16 19:01:10 2016 -0300
  Remove __ASSUME_SET_ROBUST_LIST

  commit 9ac61c0047295696cbcdbc26bdc174c7bd25a3c8
  Author: Adhemerval Zanella 
  Date:   Mon May 16 10:35:25 2016 -0300
  Remove __ASSUME_FUTEX_LOCK_PI

* Backported support into GCC for Cortex-A32, Cortex-A35, and Cortex-R8.

* Applied fix for CVE-2015-7547 - A stack-based buffer overflow in
  glibc's getaddrinfo() was corrected in glibc 2.23 and backported into
  glibc 2.21.

  https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html

* ARMv8.1 Instruction Support - ARMv8.1 instructions support was checked
  into GCC and binutils.   It has been backported into Linaro GCC 5.3
  and Linaro binutils 2.25.

* Backported -Bsymbolic-functions into Linaro binutils 2.25.

* Performance related backports from Linaro GCC 5.2-2015.11, Linaro GCC
  5.2-2015.12, and Linaro GCC 5.3-2016.01-1, Linaro GCC 5.3-2016.02,
  Linaro GCC 5.3-2016.03, Linaro GCC 5.3-2016.04, Linaro GCC
  5.4-2016.06, Linaro GCC 5.4-2016.10 and Linaro GCC 5.4-2016.12 have
  been included.

  See the following Linaro GCC snapshots:


http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.2-2015.11/

http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2015.12/

http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.01-1/

http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.02

http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.03

http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.3-2016.04

http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.4-2016.06

http://snapshots.linaro.org/components/toolchain/gcc-linaro/5.4-2016.10

http://snapshots.linaro.org/components/toolchain/gcc-

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 4.9-2017.01-rc1

[Ryan Arnold]

The Linaro Binary Toolchain


The Linaro GCC 4.9-2017.01-rc1 Release-Candidate is now available.

This is a courtesy toolchain.  The Linaro GCC 4.9 toolchain is officially
out of maintenance.  This release is being provided in order to merge in
the last FSF GCC 4.9 branch changes into the Linaro GCC 4.9 release.

Notice: All Linaro GCC 4.9 series toolchain users should migrate to the
latest version of the Linaro GCC 4 toolchain in order to mitigate
potential security exposure to CVE-2015-7547.  See the NEWS section
below for details.

Download release-candidate packages from:


http://snapshots.linaro.org/components/toolchain/gcc-linaro/4.9-2017.01-rc1/

http://snapshots.linaro.org/components/toolchain/binaries/4.9-2017.01-rc1/

Previous snapshots and release-candidates are at:

http://snapshots.linaro.org/components/toolchain/binaries/

Previous releases are at:

http://releases.linaro.org/components/toolchain/binaries/

Host Requirements
==

Linaro officially supports the current and previous Ubuntu LTS
releases (as of the time of this release).  This does not mean that
the toolchain will not work on other/older Linux distributions.  See
the following for the life-time of Ubuntu LTS releases.

https://wiki.ubuntu.com/Releases

The host system upon which the cross-compiler will run requires a
minimum of glibc 2.14, because of API changes to glibc's memcpy API.

https://bugs.linaro.org/show_bug.cgi?id=1869

Package Versions
=
Linaro GCC 4.9-2017.01-rc1

FSF eglibc 2.19 (linaro_eglibc-2_19)

Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch)

Linaro binutils 2.24 (linaro_binutils-2_24-branch)

FSF GDB 7.10 (gdb-7.10-branch)


Linaro toolchain package git branches are hosted at:

https://git.linaro.org/toolchain

NEWS for GCC 4.9 (as of Linaro GCC 4.9-2017.01-rc1)
==

* The soft-float targeted toolchains have switched to -mfloat-abi=soft
  from -mfloat-abi=softfp.

  This makes arm-linux-gnueabi and armeb-linux-gnueabi toolchains use
  “soft” FP ABI instead of “softfp”.

  Historically, TCWG’s toolchains provided both “soft” and “softfp”
  multilibs, but when switching from crosstool-ng to cbuildv2/abe (which
  support a single multilib) “softfp” multilib was choosen. Using
  “-mfloat-abi=soft” is a better choice for a gnueabi toolchain, since
  it doesn’t require cores to have a floating-point unit.

  This change should not break compatibility for toolchain users since
  the ABI will stay the same.  The compiler and glibc libraries will not
  refernce FP instructions.

* Removed .la files from binary installation as these files break
  autotools builds.

  https://bugs.linaro.org/show_bug.cgi?id=2764

* Host binaries for x86_64 linux hosts now have symbols and debug
  information stripped in order to reduce the size of the toolchain
  binary archives. This reduces the archive size from 830M to 480M for
  aarch64-linux-gnu target with the gcc-4.9-branch.

* The armv8l-linux-gnueabihf targetted toolchain is now built using
  --with-mode=thumb (like all of the other cross toolchains) rather than
  the default which is ARM mode.

* Applied fix for CVE-2015-7545 - A stack-based buffer overflow in
  glibc's getaddrinfo() was corrected in glibc 2.23 and backported into
  Linaro eglibc 2.19 (linaro_eglibc-2_19).

  https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html

* See the following Linaro GCC snapshot:

  http://snapshots.linaro.org/components/toolchain/gcc-linaro/4.9-2015.10/


Contact Linaro
===

File bugs at http://bugs.linaro.org

For Linaro member support see http://support.linaro.org

For Linaro community support email linaro-toolchain@lists.linaro.org


-- 
Ryan S. Arnold | Director - Linaro Core Technology and Tools
ryan.arn...@linaro.org | ryanarn on #linaro-tcwg @ freenode.irc.net
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 6.3-2017.02-rc1

[Ryan Arnold]

The Linaro Binary Toolchain


The Linaro GCC 6.3-2017.02-rc1 Release-Candidate is now available.

The GCC 6 Release series has significant changes from the GCC 5
release series.  For an explanation of the changes please see the
following website:

https://gcc.gnu.org/gcc-6/changes.html

For help in porting to GCC 6 please see the following explanation:

https://gcc.gnu.org/gcc-6/porting_to.html

Download release-candidate packages from:


http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.3-2017.02-rc1/

http://snapshots.linaro.org/components/toolchain/binaries/6.3-2017.02-rc1/

Previous snapshots and release-candidates are at:

http://snapshots.linaro.org/components/toolchain/binaries/

Previous releases are at:

http://releases.linaro.org/components/toolchain/binaries/

Host Requirements
==

Linaro officially supports the current and previous Ubuntu LTS
releases (as of the time of this release).  This does not mean that
the toolchain will not work on other/older Linux distributions.  See
the following for the life-time of Ubuntu LTS releases.

https://wiki.ubuntu.com/Releases

The host system upon which the cross-compiler will run requires a
minimum of glibc 2.14, because of API changes to glibc's memcpy API.

https://bugs.linaro.org/show_bug.cgi?id=1869

Package Versions
=
Linaro GCC 6.3-2017.02-rc1


http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.3-2017.02-rc1/

Linaro glibc 2.23 (linaro/2.23/master)

https://lists.gnu.org/archive/html/info-gnu/2016-02/msg9.html

Linaro newlib 2.4-2016.03 (linaro_2.4-branch)

https://sourceware.org/ml/newlib/2016/msg00370.html

Linaro binutils 2.27 (linaro_binutils-2_27-branch)


https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=binutils/NEWS;hb=refs/tags/binutils-2_27

Linaro GDB 7.12 (gdb-7.12-branch)

https://lists.gnu.org/archive/html/info-gnu/2016-10/msg7.html

Linaro toolchain package git branches are hosted at:

http://git.linaro.org/?a=project_list&s=toolchain%2F&btnS=Search

NEWS for GCC 6 (as of Linaro GCC 6.3-2017.02-rc1)
==

* The mingw toolchains are now archived using the rsync -L option in
  order to avoid problems with Windows extractors and symbolic links.

  https://review.linaro.org/#/c/16415/

  This resolves the following user bugs:

  https://bugs.linaro.org/show_bug.cgi?id=2684
  https://bugs.linaro.org/show_bug.cgi?id=2192
  https://bugs.linaro.org/show_bug.cgi?id=2762

* The soft-float targeted toolchains have now been configured to
  generate code using -mfloat-abi=soft.

  This makes arm-linux-gnueabi and armeb-linux-gnueabi toolchains use
  the "soft" FP ABI instead of "softfp".

  Historically, TCWG's toolchains provided both "soft" and "softfp"
  multilibs, but when switching from crosstool-ng to cbuildv2/abe (which
  support a single multilib) "softfp" multilib was choosen.  Using
  "-mfloat-abi=soft" is a better choice for a gnueabi toolchain, since
  it doesn't require cores to have a floating-point unit.

  This change should not break compatibility for toolchain users since
  the ABI will stay the same.  The compiler and glibc libraries will not
  refernce FP instructions.

* Removed .la files from binary toolchain archive as these files break
  autotools builds.

  https://bugs.linaro.org/show_bug.cgi?id=2764

* The Linaro GCC 6.3-2017.01 snapshot added further enablement for
  ARMv8-M.

* The Linaro GCC 6.2-2016.12 snapshot added various AArch64 bugfixes and
  optimizations.

* Backported glibc patch to simplify static malloc interposition [BZ
  #20432] to correct user identified issue.

  commit 058b5a41d56b9a8860dede14d97dd443792d064b
  Author: Florian Weimer 
  Date:   Fri Aug 26 22:40:27 2016 +0200
  malloc: Simplify static malloc interposition [BZ #20432]

* Host binaries for x86_64 linux hosts now have symbols and debug
  information stripped in order to reduce the size of the toolchain
  binary archives.  This reduces the archive size from 1.5G to 600M for
  aarch64-linux-gnu target with the gcc-6-branch.

* The GDB version was upgraded from GDB 7.11 in the Linaro GCC
  6.1-2016.08 release to GDB 7.12 in the Linaro GCC 6.2-2016.11 release.

* The Linaro GCC 6.2-2016.10 snapshot added AArch32 support for ARMv8.2
  and ARMv8m, as well as some AArch64 fixes for ARMv8.2, and bug fixes
  merged from FSF GCC 6.2.  This is available in the binary toolchain as
  of Linaro GCC 6.2-2016.11.

* Basic tuning support for the Qualcomm qdf24xx was added to the Linaro
  GCC 6.2-2016.10 snapshot and is available in the binary toolchain as
  of Linaro GCC 6.2-2016.11.

* IFUNC was disabled for baremetal targets, as it was causing test-suite
  failures, and is presently a Linux only feature.

* The gold linker was added to this binary release.

* Backpor

[ANNOUNCE] Linaro Binary Toolchain Release GCC 4.9-2017.01

[Ryan Arnold]

The Linaro Binary Toolchain


The Linaro GCC 4.9-2017.01 Release is now available.

Notice: All Linaro GCC 4.9 series toolchain users should migrate to
the latest version of the Linaro GCC 4.9 toolchain in order to
mitigate potential security exposure to CVE-2015-7547.  See the NEWS
section below for details.

Download release packages from:

http://releases.linaro.org/components/toolchain/gcc-linaro/4.9-2017.01/
http://releases.linaro.org/components/toolchain/binaries/4.9-2017.01/

Previous snapshots and release-candidates are at:

http://snapshots.linaro.org/components/toolchain/binaries/

Previous releases are at:

http://releases.linaro.org/components/toolchain/binaries/

A description of what each ABI or triplet is can be found at:


https://collaborate.linaro.org/display/TCWGPUB/ARM+and+AArch64+Target+Triples

Host Requirements
==

Linaro officially supports the current and previous Ubuntu LTS
releases (as of the time of this release).  This does not mean that
the toolchain will not work on other/older Linux distributions.  See
the following for the life-time of Ubuntu LTS releases.

https://wiki.ubuntu.com/Releases

The host system upon which the cross-compiler will run requires a
minimum of glibc 2.14, because of API changes to glibc's memcpy API.

https://bugs.linaro.org/show_bug.cgi?id=1869

Package Versions
=
Linaro GCC 4.9-2017.01

  http://releases.linaro.org/components/toolchain/gcc-linaro/4.9-2017.01/

FSF eglibc 2.19 (linaro_eglibc-2_19)

  
http://www.eglibc.org/cgi-bin/viewvc.cgi/branches/eglibc-2_19/libc/NEWS?view=markup

Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch)

  https://sourceware.org/ml/newlib/2013/msg01128.html

Linaro binutils 2.24 (linaro_binutils-2_24-branch)

  
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=binutils/NEWS;hb=refs/tags/binutils-2_24

FSF GDB 7.10 (gdb-7.10-branch)

  https://sourceware.org/ml/gdb-announce/2015/msg5.html


Linaro toolchain package git branches are hosted at:

http://git.linaro.org/toolchain

NEWS for GCC 4.9 (as of Linaro GCC 4.9-2017.01)
==
* The soft-float targeted toolchains have switched to -mfloat-abi=soft
  from -mfloat-abi=softfp.

  This makes arm-linux-gnueabi and armeb-linux-gnueabi toolchains use
  “soft” FP ABI instead of “softfp”.

  Historically, TCWG’s toolchains provided both “soft” and “softfp”
  multilibs, but when switching from crosstool-ng to cbuildv2/abe (which
  support a single multilib) “softfp” multilib was choosen. Using
  “-mfloat-abi=soft” is a better choice for a gnueabi toolchain, since
  it doesn’t require cores to have a floating-point unit.

  This change should not break compatibility for toolchain users since
  the ABI will stay the same.  The compiler and glibc libraries will not
  refernce FP instructions.

* Host binaries for x86_64 linux hosts now have symbols and debug
  information stripped in order to reduce the size of the toolchain
  binary archives. This reduces the archive size from 830M to 480M for
  aarch64-linux-gnu target with the gcc-4.9-branch.

* Removed .la files from binary installation as these files break
  autotools builds.

  https://bugs.linaro.org/show_bug.cgi?id=2764

* The mingw toolchains are now archived using the rsync -L option in
  order to avoid problems with Windows extractors and symbolic links.

  https://review.linaro.org/#/c/16415/

  This resolves the following user bugs:

  https://bugs.linaro.org/show_bug.cgi?id=2684

  https://bugs.linaro.org/show_bug.cgi?id=2192

  https://bugs.linaro.org/show_bug.cgi?id=2762

* Copy the libwinpthread DLL into the bin directories so it gets into
  the tmp directory before tar is run.

  https://review.linaro.org/#/c/13723/

* Applied fix for CVE-2015-7547 - A stack-based buffer overflow in
  glibc's getaddrinfo() was corrected in glibc 2.23 and backported into
  Linaro eglibc 2.19 (linaro_eglibc-2_19).

  https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html


Contact Linaro
===

File bugs at http://bugs.linaro.org

For Linaro member support see http://support.linaro.org

For Linaro community support email linaro-toolchain@lists.linaro.org


-- 
Ryan S. Arnold | Director - Linaro Core Technology and Tools
ryan.arn...@linaro.org | ryanarn on #linaro-tcwg @ freenode.irc.net
T: +1-612-424-1861
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

[ANNOUNCE] Linaro Binary Toolchain Release GCC 5.4-2017.01

[Ryan Arnold]

The Linaro Binary Toolchain


The Linaro GCC 5.4-2017.01 Release is now available.

Notice: All Linaro GCC 5 series toolchain users should migrate to the
latest version of the Linaro GCC 5 toolchain in order to mitigate
potential security exposure to CVE-2015-7547.  See the NEWS section
below for details.

Download release packages from:

(sources)
http://releases.linaro.org/components/toolchain/gcc-linaro/5.4-2017.01/
(binaries)
http://releases.linaro.org/components/toolchain/binaries/5.4-2017.01/

Previous snapshots and release-candidates are at:

http://snapshots.linaro.org/components/toolchain/binaries/

Previous releases are at:

http://releases.linaro.org/components/toolchain/binaries/

A description of what each ABI or triplet is can be found at:


https://collaborate.linaro.org/display/TCWGPUB/ARM+and+AArch64+Target+Triples

Host Requirements
==

Linaro officially supports the current and previous Ubuntu LTS
releases (as of the time of this release).  This does not mean that
the toolchain will not work on other/older Linux distributions.  See
the following for the life-time of Ubuntu LTS releases.

https://wiki.ubuntu.com/Releases

The host system upon which the cross-compiler will run requires a
minimum of glibc 2.14, because of API changes to glibc's memcpy API.

https://bugs.linaro.org/show_bug.cgi?id=1869

Package Versions
=
Linaro GCC 5.4-2017.01

  http://releases.linaro.org/components/toolchain/gcc-linaro/5.4-2017.01/

Linaro glibc 2.21 (linaro/2.21)

  https://lists.gnu.org/archive/html/info-gnu/2015-02/msg1.html

Linaro newlib 2.1.0-2014.09 (linaro_newlib-branch)

  https://sourceware.org/ml/newlib/2013/msg01128.html

Linaro binutils 2.25 (linaro_binutils-2_25-branch)

  
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=binutils/NEWS;hb=refs/tags/binutils-2_25

FSF GDB 7.12 (gdb-7.12-branch)

  https://lists.gnu.org/archive/html/info-gnu/2016-10/msg7.html

Linaro toolchain package git branches are hosted at:

http://git.linaro.org/toolchain

NEWS for GCC 5 (as of Linaro GCC 5.4-2017.01)
==
* The soft-float targeted toolchains have now been configured to
  generate code using -mfloat-abi=soft.

  This makes arm-linux-gnueabi and armeb-linux-gnueabi toolchains use
  the “soft” FP ABI instead of “softfp”.

  Historically, TCWG’s toolchains provided both “soft” and “softfp”
  multilibs, but when switching from crosstool-ng to cbuildv2/abe (which
  support a single multilib) “softfp” multilib was choosen. Using
  “-mfloat-abi=soft” is a better choice for a gnueabi toolchain, since
  it doesn’t require cores to have a floating-point unit.

  This change should not break compatibility for toolchain users since
  the ABI will stay the same. The compiler and glibc libraries will not
  refernce FP instructions.

* Include GCC fix for Linaro bugzilla #2562:

  ARM GCC 5.2 call weak function instead of strong when called through
  pointer

  https://bugs.linaro.org/show_bug.cgi?id=2562

* Include GCC fix for Linaro bugzilla #1925:

  [regression] FAIL: libgomp.fortran/retval1.f90 -O1 execution test

  https://bugs.linaro.org/show_bug.cgi?id=1925

* Include GCC fix for Linaro bugzilla #2185:

  aarch64-linux-gnu-g++ internal compiler error: in curr_insn_transform

  https://bugs.linaro.org/show_bug.cgi?id=2185

* Backported glibc patch to simplify static malloc interposition [BZ
  #20432] to correct user identified issue.

  commit 058b5a41d56b9a8860dede14d97dd443792d064b
  Author: Florian Weimer
  Date: Fri Aug 26 22:40:27 2016 +0200
  malloc: Simplify static malloc interposition [BZ #20432]

* Host binaries for x86_64 linux hosts now have symbols and debug
  information stripped in order to reduce the size of the toolchain
  binary archives. This reduces the archive size from 1.1G to 580M for
  aarch64-linux-gnu target with the gcc-5-branch.

* Removed .la files from binary toolchain archive as these files break
  autotools builds.

  https://bugs.linaro.org/show_bug.cgi?id=2764

* The mingw toolchains are now archived using the rsync -L option in
  order to avoid problems with Windows extractors and symbolic links.

  https://review.linaro.org/#/c/16415/

  This resolves the following user bugs:

  https://bugs.linaro.org/show_bug.cgi?id=2684

  https://bugs.linaro.org/show_bug.cgi?id=2192

  https://bugs.linaro.org/show_bug.cgi?id=2762

* Copy the libwinpthread DLL into the bin directories so it gets into
  the tmp directory before tar is run.

  https://review.linaro.org/#/c/13723/

* Increment binutils release date to 2016_02 to reflect the most recent
  commit:

  commit ef90a4718f535cbe6345b4e7168baea7b1972abf
  Author: Matthew Wahab 
  Date:   Tue Jan 12 16:35:30 2016 +
  [ARM] Support ARMv8.2 RAS extension.

* Baremetal sysroot names now 

[ANNOUNCE] Linaro Binary Toolchain Release-Candidate GCC 6.3-2017.02-rc2

[Ryan Arnold]

The Linaro Binary Toolchain


The Linaro GCC 6.3-2017.02-rc2 Release-Candidate is now available.

The GCC 6 Release series has significant changes from the GCC 5
release series.  For an explanation of the changes please see the
following website:

https://gcc.gnu.org/gcc-6/changes.html

For help in porting to GCC 6 please see the following explanation:

https://gcc.gnu.org/gcc-6/porting_to.html

Download release-candidate packages from:

(sources)
http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.3-2017.02-rc2/
(binaries)
http://snapshots.linaro.org/components/toolchain/binaries/6.3-2017.02-rc2/

Previous snapshots and release-candidates are at:

http://snapshots.linaro.org/components/toolchain/binaries/

Previous releases are at:

http://releases.linaro.org/components/toolchain/binaries/

A description of the arm and Aarch64 target triples can be found at:


https://collaborate.linaro.org/display/TCWGPUB/ARM+and+AArch64+Target+Triples

Host Requirements
==

Linaro officially supports the current and previous Ubuntu LTS
releases (as of the time of this release).  This does not mean that
the toolchain will not work on other/older Linux distributions.  See
the following for the life-time of Ubuntu LTS releases.

https://wiki.ubuntu.com/Releases

The host system upon which the cross-compiler will run requires a
minimum of glibc 2.14, because of API changes to glibc's memcpy API.

https://bugs.linaro.org/show_bug.cgi?id=1869

Package Versions
=
Linaro GCC 6.3-2017.02-rc2


http://snapshots.linaro.org/components/toolchain/gcc-linaro/6.3-2017.02-rc2/

Linaro glibc 2.23 (linaro/2.23/master)

https://lists.gnu.org/archive/html/info-gnu/2016-02/msg9.html

Linaro newlib 2.4-2016.03 (linaro_2.4-branch)

https://sourceware.org/ml/newlib/2016/msg00370.html

Linaro binutils 2.27 (linaro_binutils-2_27-branch)


https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=binutils/NEWS;hb=refs/tags/binutils-2_27

Linaro GDB 7.12 (gdb-7.12-branch)

https://lists.gnu.org/archive/html/info-gnu/2016-10/msg7.html

Linaro toolchain package git branches are hosted at:

http://git.linaro.org/toolchain

NEWS for GCC 6 (as of Linaro GCC 6.3-2017.02-rc2)
==

* Previous versions of the Linaro GCC 6 toolchain were incorrectly
  generating floating-point code for soft-float Linux targets
  (arm-linux-gnueabi, and armeb-linux-gnueabi).  This escaped detection
  until recently because the soft-float targeted toolchains were
  configured to use general-purpose registers for passing floating-point
  values (which is what you would expect for soft-float toolchains) and
  the intra-routine floating-code was not noticed.

  The issue would only show up on targets that were run on hardware that
  truly didn't have floating-point hardware where the kernel did not
  trap and emulate floating-point routines.  This has been solved in
  Linaro GCC 6.3-2017.02-rc2 by configuring the toolchain (using
  --with-float=soft) to generate code without any floating-point
  instructions at all (-mfloat-abi=soft).

  https://review.linaro.org/#/c/16968/2

  This change should not break compatibility between existing binaries
  compiled with these toolchains since the float-point parameter passing
  ABI is still the same.

* 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 inconsistent 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.

  GCC PR target/78253: [5/6/7 Regression] [ARM] call weak function
  instead of strong when called through pointer.

  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78253

  Linaro bugzilla #2562: ARM GCC 5.2 call weak function instead of
  strong when called through pointer

  https://bugs.linaro.org/show_bug.cgi?id=2562

* 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:

  https://bugs.linaro.org/show_bug.cgi?id=2684
  https://bugs.linaro.org/show_bug.cgi?id=2192
  https://bugs.linaro.org/show_bug.cgi?id=2762

  This has been solved by copying files rather than using symlinks when
  the mingw targetted toolchain archives are created.

  https://review.linar

[ANNOUNCE] Linaro Binary Toolchain Release GCC 6.3-2017.02

[Ryan Arnold]

The Linaro Binary Toolchain


The Linaro GCC 6.3-2017.02 Release is now available.

The GCC 6 Release series has significant changes from the GCC 5
release series.  For an explanation of the changes please see the
following website:

https://gcc.gnu.org/gcc-6/changes.html

For help in porting to GCC 6 please see the following explanation:

https://gcc.gnu.org/gcc-6/porting_to.html

Download release packages from:

(sources)
http://releases.linaro.org/components/toolchain/gcc-linaro/6.3-2017.02/
(binaries)
http://releases.linaro.org/components/toolchain/binaries/6.3-2017.02/

Previous snapshots and release-candidates are at:

http://snapshots.linaro.org/components/toolchain/binaries/

Previous releases are at:

http://releases.linaro.org/components/toolchain/binaries/

Supported Targets
==

The Linaro binary toolchain is a collection of x86-hosted GNU
cross-toolchains targeting a variety of ARM architecture targets.
Linaro TCWG provides these toolchains as a service to our members.
Due to hardware availability, system-image availability, validation
complexity, and user-base size, not all host and target toolchain
combinations can be validated by Linaro with the same rigor.

The most rigorously validated targets are little-endian and hardfloat
implementations of the 32-bit ARMv7 (arm), 32-bit ARMv8 (armv8), and
64-bit ARMv8 (aarch64) architectures.  Linaro recommends those targets
to our members.

A full list of the supported arm and AArch64 target triples can be
found here:


https://collaborate.linaro.org/display/TCWGPUB/ARM+and+AArch64+Target+Triples

Host Requirements
==

Linaro officially supports the current and previous Ubuntu LTS
releases (as of the time of this release).  This does not mean that
the toolchain will not work on other/older Linux distributions.  See
the following for the life-time of Ubuntu LTS releases.

https://wiki.ubuntu.com/Releases

The host system upon which the cross-compiler will run requires a
minimum of glibc 2.14, because of API changes to glibc's memcpy API.

https://bugs.linaro.org/show_bug.cgi?id=1869

Linaro recommends using the 64-bit x86_64 host toolchains as the
32-bit i686 host toolchains and the 32-bit mingw host toolchains will
only be provided as long as there is sufficient member interest to
justify their continued availability.

Package Versions
=
Linaro GCC 6.3-2017.02

http://releases.linaro.org/components/toolchain/gcc-linaro/6.3-2017.02/

Linaro glibc 2.23 (linaro/2.23/master)

https://lists.gnu.org/archive/html/info-gnu/2016-02/msg9.html

Linaro newlib 2.4-2016.03 (linaro_2.4-branch)

https://sourceware.org/ml/newlib/2016/msg00370.html

Linaro binutils 2.27 (linaro_binutils-2_27-branch)


https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=blob_plain;f=binutils/NEWS;hb=refs/tags/binutils-2_27

Linaro GDB 7.12 (gdb-7.12-branch)

https://lists.gnu.org/archive/html/info-gnu/2016-10/msg7.html

Linaro toolchain package git branches are hosted at:

http://git.linaro.org/toolchain

NEWS for GCC 6 (as of Linaro GCC 6.3-2017.02)
==

* Previous versions of the Linaro GCC 6 toolchain were incorrectly
  generating floating-point code for soft-float Linux targets
  (arm-linux-gnueabi, and armeb-linux-gnueabi).  This escaped detection
  until recently because the soft-float targeted toolchains were
  configured to use general-purpose registers for passing floating-point
  values (which is what you would expect for soft-float toolchains) and
  the intra-routine floating-code was not noticed.

  The issue would only show up on targets that were run on hardware that
  truly didn't have floating-point hardware where the kernel did not
  trap and emulate floating-point routines.  This has been solved in
  Linaro GCC 6.3-2017.02-rc2 by configuring the toolchain (using
  --with-float=soft) to generate code without any floating-point
  instructions at all (-mfloat-abi=soft).

  https://review.linaro.org/#/c/16968/2

  This change should not break compatibility between existing binaries
  compiled with these toolchains since the float-point parameter passing
  ABI is still the same.

* 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 inconsistent 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.

  GCC PR target/78253: [5/6/7 Regression] [ARM] call weak function
  instead of strong when called through pointer.

  https://gcc.gnu