linaro-toolchain

linaro-toolchain@lists.linaro.org

1 participants
5666 discussions

by Charles Baylis

== Progress == Sick leave [2/10] Patch submission for vldN_lane [1/10] Attempting to run SPEC2k6 on Juno [6/10] Misc [1/10] irc support, openjdk suspected compiler bug, meetings, mailing lists

11 years, 3 months

[ACTIVITY] Week 42

by Yvan Roux

== Issues == * Still no network at home and will not be fixed before at least one week :( == Progress == * GCC 4.9 2014.10 (8/10) - Merged FSF 4.9 branch - Released Linaro 4.9 2014.10 * Misc: (2/10) - Various meetings. == Plan == * Analyse some failures that occur only in --enable-release.

11 years, 3 months

[ACTIVITY] 13 - 17 October 2014

by Omair Javaid

== Progress == Catch up with work after return from Eid ul Adha and Annual Holidays [7/10] * Hong Kong visa application * UPS repairs and office cleanup * Catching up with work, gdb roadmap and open/running cards. * Emails/Patch scrolling/Meetings etc * Sick day off on Monday GDB Tracepoints/Fast Tracepoints support on arm [TCWG-480] [3/10] * Getting re-synced with code where I left. == Plan == Further progress on GDB Tracepoints/Fast Tracepoints support on arm [TCWG-480] Investigate possibility of AArch64 trace-point work without availability of hardware. Check for GDB status on ARM and AArch64 vs x86.

11 years, 3 months

[Weekly] 13-17 OCT 2014

by Michael Collison

== This week == * GCC Modularization Project (5/10) - Reviewed previous documentation by Joseph Meyers - Reviewed source base to understand issues * Linaro bugzilla 602 - gcc 4.7.3 compiler internal error while building hsail components (3/10) - Reproduced with 4.7. Triage indicates coding error (operands reversed) - Continuing investigation to determine if issue exists with 4.8 and 4.9 * Linaro bugzilla 539 - .LTHUNK symbols are surviving (1/10) - Preliminary investigation and triage * Misc. (1/10) - Conference calls == Next week == - Draft plan for GCC modularization for review - Resolve bugzilla 602 - Continue investigation of bugzilla 602 - conduct interview with Prathamesh Kulkarni

11 years, 3 months

[ACTIVITY] 13 - 17 October 2014

by Kugan

== Progress == * Zero/sign extension elimination with widening types (TCWG-546 - 9/10) - Fixed ICEs and now can build the cross compiler and do the regression testing with qemu - some test-cases are failing due to condition that rely on overflow; this need fixing. - Bootstrapping on AArch64 still fails (but much later than previously). - Verified CRC is optimized * Improve block memory operations by GCC (TCWG-142 - 1/10) - Looked at the changes since the card was drafted == Plan == * Continue with Zero/sign extension pass.

11 years, 3 months

[ACTIVITY] 13-17 October 2014

by Christophe Lyon

== Progress == * GCC trunk/4.9 validation (CARD-647) (3/10) - committed testsuite patch to test if -shared is supported - forcing -mword-relocations flags when compiling testglue works on my Ubuntu machines, but does not in the Compute Farm RHEL5 servers. - investigating why, all the more as it made me incorrectly report failures in the 4.9 branch * Validation (2/10) - compared cbuild2 schroot-test branch and master the results of this manual run does not seem to match Jenkins results * Neon intrinsics tests (1/10) - fixed .exp harness to support parallelization - looking at how to pre-support fp16, will probably skip it for now, and add dedicated tests later * AArch64 sanitizer (1/10) - GCC trunk seems to need to cherry pick a sanitizer patch when building using recent kernel headers - tried to use Jenkins to build trunk and trunk+cherry-pick, but the results are not consistent needs more investigation * Misc (3/10) - calls, meetings, irc == Next == * GCC trunk/4.9 cross-validation - fix -mword-relocations support - investigate abi_check test * AArch64 sanitizer * Neon intrisics tests update * cbuild2: - analyze previous results (mostly check the logs....) - look at backport-test script + logs Short next week: off Wednesday/Thursday

11 years, 3 months

[ACTIVITY] 13 - 17 October 2014

by Will Newton

== Progress == * Respin of malloc single-thread optimizations (4/10, TCWG-436) - Create a generic header, include AArch64 in series * Further work on malloc app benchmark framework (4/10, TCWG-441) - Cleaned up, improved reliability, added comments - Committed to cortex-malloc.git * Email, meetings, etc. (1/10) * Upstream work (1/10, CARD-341) - glibc patch review and pings - Look into some bug reports and testsuite failures == Issues == * Electricians and gas engineers turning off power/heating at various points == Plan == * Hopefully get some resolution of single thread atomic stuff for glibc -- Will Newton Toolchain Working Group, Linaro

11 years, 3 months

[ACTIVITY] Week 42

by Renato Golin

== Progress == * Linux Plumbers (6/10) - Attended conference, Android/Tools/LLVM tracks - Presented 2 talks (GCC+LLVM and LLVM+ARM) * Buildbots (TCWG-76 2/10) - Made the Compiler-RT bot green! Now on to the libc++ one * Background (2/10) - Code review, meetings, discussions, etc. - Internet upgrade, re-wiring the house, building works == Plan == * Add libc++abi buildbot * Follow up on the fpu issues on Clang/asm

11 years, 3 months

Prebuilt binary download for gcc-linaro 4.8.4

by Rick Liu

Hi, In release 14.08, Linaro GCC 4.8 2014.08 is based off GCC 4.8.4+svn213802. [http://releases.linaro.org/14.08/components/toolchain/gcc-linaro/4.8] However, in toolchain/binaries, [http://releases.linaro.org/14.08/components/toolchain/binaries] I can't find the download for the prebuilt binaries for gcc-linaro-arm-linux-gnueabihf-4.8. I only found the download for 4.9 version. It seems the last 4.8 version binary existed in 2014.04 release only? [http://releases.linaro.org/14.04/components/toolchain/binaries] Where can I get the prebuilt binary of gcc-linaro-arm-linux-gnueabihf-4.8-2014.08_linux.tar.bz2? Thanks, Rick

11 years, 3 months

Re: [PATCH] ARM: Blacklist GCC 4.8.0 to GCC 4.8.2 - PR58854 (fwd)

by Nicolas Pitre

FYI. The whole thread is available here: http://article.gmane.org/gmane.linux.ports.arm.omap/119412 ---------- Forwarded message ---------- Date: Thu, 16 Oct 2014 01:18:01 +0100 From: Russell King - ARM Linux <linux(a)arm.linux.org.uk> To: Peter Hurley <peter(a)hurleysoftware.com> Cc: Nathan Lynch <Nathan_Lynch(a)mentor.com>, David Laight <David.Laight(a)ACULAB.COM>, Otavio Salvador <otavio(a)ossystems.com.br>, Linus Torvalds <torvalds(a)linux-foundation.org>, Nicolas Pitre <nico(a)fluxnic.net>, Linux OMAP Mailing List <linux-omap(a)vger.kernel.org>, linux-arm-kernel(a)lists.infradead.org Message-ID: <20141016001801.GQ12379(a)n2100.arm.linux.org.uk> Subject: Re: [PATCH] ARM: Blacklist GCC 4.8.0 to GCC 4.8.2 - PR58854 On Wed, Oct 15, 2014 at 06:18:30PM -0400, Peter Hurley wrote: > On 10/15/2014 05:56 PM, Russell King wrote: > > I was in two minds whether to include 4.8.3 as Linaro released a buggy > > toolchain which identifies itself as 4.8.3, but I decided that's also > > a distro problem. IMHO Linaro should really think about taking that > > compiler down given the seriousness of this bug and it being > > indistinguishable from the fixed stock version. > > Maybe it's unfair to blame them; Linaro just took a snapshot and > released what was there. > > If gcc is going to retain the "change release number then add all the > new features" model, some kind of prerelease indicator would help > eliminate this kind of problem. And that indicator should be both > a preprocessor define and parseable from the command line :) My comment is not to attribute blame to them, my comment is entirely on a technical level. My reasoning is that the bug is just as prevalent in userspace, though it will occur less often. Any program which uses signal handlers is a candidate for exactly the same kind of corruption, since you can receive that signal between the point that the stack pointer is modified and the function loads the parent context. Of course, there are ways around that: don't use signal handlers, or if you do, use alternate signal stacks. Neither of those can be guaranteed for any program though. So, let me put this another way: a compiler with this bug is _completely_ unsuitable for use for compiling programs for use under the Linux kernel _as well_ as the Linux kernel itself. The difference is that the Linaro compilers come with an expectation that they are usable on ARM... whereas stock versions cover a lot more and so the ARM arch is probably very small number of their users. Hence why I recommend that Linaro takes down their buggy compiler. Their 4.8.3 version should not be used *anywhere*, just the same as the stock 4.8 to 4.8.2 inclusive should also not be used anywhere on ARM either.

11 years, 3 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain