[ACTIVITY] Week 43

2014-10-24 Thread Charles Baylis
=== Progress === SPEC Benchmarking [5/10] . managed to run SPEC2k . managed to run integer parts of SPEC2k6 . spec2xxx-report fails . can't run full suite as LAVA Junos have insufficient disk NEON error reporting bugs #403/#418 [3/10] . ongoing mailing list discussions vldN_lane patches [1

[ACTIVITY] 20-24 October 2014

2014-10-24 Thread Christophe Lyon
Short week, 2 days off == Progress == * GCC trunk/4.9 cross-validation (2/10) - committed testsuite patch to support forcing -mword-relocations option when compiling testglue.c * Neon intrinsics tests (2/10) - committed the 1st batch (21 commits) * AArch64 sanitizer - libsanitizer interna

[ACTIVITY] Week 43

2014-10-24 Thread Renato Golin
== Progress == * Automation Framework (CARD-1378 1/10) - Setting up Junos with ARM * Toolchain (CARD-862 1/10) - Some progress on fpu parser issue - Produced a lot more work for the near future * Buildbots (TCWG-76 4/10) - Setting up a libc++ buildbot, working on reducing failures - Some bo

[ACTIVITY] 20 - 24 October 2014

2014-10-24 Thread Will Newton
== Progress == * Released Linaro glibc 2.20 2014.11 (2/10) * Released Linaro binutils 2.24 2014.11-2 (2/10) * Investigate gdb and Coresight integration possibilities (1/10) * Email, meetings, etc. (1/10) * Upstream work (4/10, CARD-341) - Patch review - Look binutils testsuite failures on ARM, s

Re: [RFC] Linaro release version number macros

2014-10-24 Thread Christopher Covington
On 10/24/2014 10:20 AM, Christophe Lyon wrote: > On 23 October 2014 12:00, Will Newton wrote: >> On 23 October 2014 10:44, Yvan Roux wrote: >>> Hi, >>> >>> after the recent lkml thread on blacklisting some GCC versions (see >>> below) and the issue in identifying accurately our releases, I propos

Re: [RFC] Linaro release version number macros

2014-10-24 Thread Christophe Lyon
On 23 October 2014 12:00, Will Newton wrote: > On 23 October 2014 10:44, Yvan Roux wrote: >> Hi, >> >> after the recent lkml thread on blacklisting some GCC versions (see >> below) and the issue in identifying accurately our releases, I propose >> to add some Linaro specific macros in our branche

Re: [ANNOUNCE] Linaro GCC 4.9 2014.10 released

2014-10-24 Thread Yvan Roux
Hi Matthias, Indeed there is a big issue with the branch merge. It is not a typo in the revision, I did a merge from r216130 but only a subset of the modification were committed, which is really weird as the merge is done via "svn merge", we're creating a git branch for our validation from the sv