linaro-toolchain

linaro-toolchain@lists.linaro.org

4 participants
5631 discussions

by Yvan Roux

== Progress == o Linaro GCC (6/10) * More backports * Compared our various flavor of validation results * Looked at bug reports and mailing list questions on our last snapshot. o Upstream work (2/10) * Continue on sanitizing gfortran testsuite o Misc (2/10) * Various meetings * Discussed benchmarking infra with Bernie == Plan == o GCC 5.3 branch merge o Continue on-going tasks o Tuesday Off

9 years, 9 months

[ACTIVITY] 30th November - 4th December

by Bernie Ogden

Holiday [2/10] Port to microinstance - TCWG-432 [1/10] * Set up reporting for CPU2006 * Learned how to generate metadata, but not how to use it Trigger benchmarks on backports - TCWG-352 [2/10] * Figured out the rough shape * Created, didn't test, rough implementation TCWG-354 [3/10] * Build/run scaffolding for CoreMark Pro * Working for manual runs Misc [2/10] * Input validation for dispatcher script * Meeting with Ade on LAVA benchmarking * Meetings/mail/etc =Plan= Review, test, debug build-triggers-benchmark job Check CoreMark Pro run configuration, enable for automatic runs Review security with shared uinstance/main instance code Expose more data, benchmarks to bundles Debug/test Jenkins job in microinstance Create bootable image for at least 1 target, or know what the problems are Write up noise control report (if time) More support for SPEC-on-Android?

9 years, 9 months

[ACTIVITY] 30 Nov to 4 Dec 2015

by Prathamesh Kulkarni

* TCWG-72 (2/10) - Added new target hook to generate target-specific divmod libfunc - Builds cleanly now on x86_64, arm and arm-linux-gnueabihf - Sent to tcwg list for review * LTO spec2k6 build (2/10) - Built speck26 with LTO * Target hook (4/10) - Completed with ASM_OUTPUT_LABEL_REF - In progress - SIZE_ASM_OP to data hook, ASM_OUTPUT_SIZE_DIRECTIVE, ASM_OUTPUT_MEASURED_SIZE * Benchmarking (1/10) - tcwg-319: Job in progress for fp benchmarks with patch - tcwg-310 (loop peeling): Submitted job for running 252.eon - Both the jobs failed due to lab downtime, need to be re-run. - Received job template from Bernie for running benchmarks on cortex-a15. * Misc (1/10) - Meetings == Next Week == - Continue benchmarking spec2k6 with LTO - Look at bugs exposed by speck2k6 LTO build - Benchmarking tcwg-319, tcwg-310

9 years, 9 months

[Weekly] 30 November - 4 December 2015

by Michael Collison

== This week == * TCWG-317 - Exploit wide add operations when appropriate for Aarch32 (0/10) - No comments/review upstream will ping for update * TCWG-316 - Exploit vector multiply by scalar instructions (4/10) - Code improvements will require standard name for vectorizer and new patterns - On hold until GCC 6 is released * Bugzilla 68543 - [AArch64] Implement overflow arithmetic standard names (3/10) - Initial investigation * Bugzilla 68532 - [ARM] Incorrect code result on arm big endian (2/10) - Investigation into understanding how vectorizer represents lanes vs arm big endian back end - Solution suspended until I can coordinate with Charlie * Misc (1/10) - Conference calls == Next week == * Bugzilla 68543 - Implement add and subtract overflow operations and test * TCWG-317 - Ping upstream and respond to upstream feedback * Bugzilla 68532 - Coordinate with Charlie

9 years, 9 months

[ACTIVITY]

by Renato Golin

== Progress == * Ill (4/10) * Support (1/10) - Bugzilla issues (PR20490, PR24635, PR24350, PR20025, PR25720, PR25722) * Benchmarks (1/10) - Checking some previous benchmark results on A57 * Buildbots (2/10) - Getting AArch64 full bot back to rotation, since it's stable now - Re-enabling libc++ prototypes on local master - Bisecting broken test-suite - Another power cut in the office sent all the bots down... :( * Background (2/10) - Code review, meetings, discussions, general support, etc. - Validating some old sanitizer bugs - FOSDEM admin

9 years, 9 months

[ACTIVITY] 30th Nov - 04th Dec

by Yao Qi

* One day off on Monday. # Progress # * Answer ST questions about supporting multi-arch with ST jtag probe. [1/10] * TCWG-171, Enable gdb core file tests when testing remotely, [3/10]. Ongoing. * Run gdb.base/sizeof.exp with board having gdb,noinferiorio. Done. [1/10] * TCWG-460, mutli-arch follow-up work, teach AArch64 GDBserver understand ARM breakpoint instructions. Patch is approved. [2/10]. * TCWG-424, fail in gdb.base/random-signal.exp. [1/10] Root cause is identified, need to figure out how to fix it in next step. * Review ARM GDBserver software single step patch V4. # Plan # * TCWG-171, TCWG-156, TCWG-424. * Review ARM GDBserver software single step patch V5, which should be the final version, I hope. -- Yao

9 years, 9 months

[ACTIVITY] Nov 30- Dec 4, 2015

by Christophe Lyon

== Progress == * Validation - a few cleanup patches in the comparison scripts - contribute to debug of ptys allocation problems: the tests pass when executed outside of our schroots. - improvements in the reports from the validation done in the ST Compute Farm - reported a few regressions * GCC - cleanup patch for target attributes tests, - pr68620 (fp16 transfers in big-endian mode) * Misc (conf calls, meetings, emails, ....) == Next == * Validation: monitoring, improvements * GCC: bug fixes, cleanup

9 years, 9 months

GNU GCC development plan and its interaction with Linaro

by Virendra Kumar Pathak

Hi Linaro Toolchian Group, I am new to GCC development and have some basic question on its development process. Could you please give some insight on below questions. (Apology if they are very trivial). I have read https://gcc.gnu.org/develop.html If I am correct, gcc trunk is on gcc 6.0.0 (stage 3) at present and will becomes 6.0.1 (regression fix only) in January 2016. gcc 6.0.1 will be released as gcc 6.1.0 in April, 2016 and from there onwards gcc 6 release branch will start. However, There is also a gcc 5 branch in parallel whose current version is 5.2.1 and will be released as gcc 5.3 soon. Hopefully gcc 5.3 would be the last release in gcc 5 series. (Please correct me if I am wrong). [Questions] 1. What is the difference between experimental(gcc 6.0.0 stage 3) & gcc release branch (gcc 5.2.1)? Is there any rule which decides which changes will go where? In case, I have some patches for new aarch64 processor at present, in which branch these changes would be merged (assuming they passes reviews)? 2. How is the subversion of release branches are decided? Is it correct to say that there will be always 3 subversion of any release branch (e.g. gcc 5.1, gcc 5.2 & gcc 5.3)? 3. What is the working model between GNU GCC and Linaro GCC? Does Linaro directly accept patches? or they need to go to GNU GCC first? Thanks in advance for your time. with regards, Virendra Kumar Pathak -- with regards, Virendra Kumar Pathak

9 years, 9 months

Fwd: Lost upstream patch in merge from gcc-5-branch to linaro/gcc-5-branch

by Robert Schiele

Keeping linaro-toolchain in the loop. Robert ---------- Forwarded message ---------- From: Robert Schiele <rschiele(a)gmail.com> Date: Thu, Dec 3, 2015 at 4:44 PM Subject: Re: Lost upstream patch in merge from gcc-5-branch to linaro/gcc-5-branch To: Yvan Roux <yvan.roux(a)linaro.org> Hi Yvan, On Thu, Dec 3, 2015 at 1:25 PM, Yvan Roux <yvan.roux(a)linaro.org> wrote: > This fix on gcc-5-branch doesn't apply on Linaro 5 branch, because we > have backported trunk revision 222624 (which renames maybe_fma to > coumpound_p) into it. So, our branch as the same code as trunk one > regarding aarch64_rtx_costs. Do you experiment any issues related to > this change ? No issues. This was just a theoretical thought and through our CI build I learned exactly what you just told me the hard way now. Sorry for the noise. Robert

9 years, 9 months

Bug: Linaro ABE abe.sh doesn't allow timeout > 10 seconds

by Christopher Roberts

abe.sh in the ABE framework accepts a parameter to set the wget timeout when it fetches snapshots (default 10s); however that parameter has an upper threshold of 10 seconds (condition at line 996 only sets timeout to specified value if < 11). Is this intentional? It seems like it would make more sense to give it a floor instead of a ceiling or perhaps not limit the range of potential values at all. Best regards, Chris Roberts

9 years, 9 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain