linaro-toolchain

linaro-toolchain@lists.linaro.org

5 participants
5605 discussions

by Yvan Roux

1 day off (2/10) == Issues == * none. == Progress == * GCC 4.9 and 4.8 2014.11 (6/10) - Backported ILP32 related commits in 4.9 - Validate and committed Linaro release macros in Linaro branches. - Released 4.9 and 4.8 2014.11 * Lab move (1/10) - Tested new validation infrastructure. * Misc: (1/10) - Finished libunwind task - Various meetings. == Plan == * Back on backports

10 years, 7 months

[ACTIVITY] 10th - 14th November

by Bernie Ogden

cbuild2 benchmarking - TCWG-360 [5/10] * Fixed some bugs and did some general tidying up * Pulled SPEC2000 into my framework * Did some test runs on local machines, looks promising libm exercising - TCWG-558 [3/10] * Much fiddling with one benchmark (MCB) * Experimented, thought about methodology Meetings/mail/etc - [2/10] =Plan= cbuild2 benchmarking * Tweak eembc - it worked before, but spec forced me to change the scripts a little * Test in LAVA/new TCWG infrastructure when available * Test repeatability (depends on above) * Possibly have another go at building tools on AArch64 libm exerising * Work through the most interesting benchmarks with a fixed method * Hopefully reach the end and do some analysis

10 years, 7 months

[ACTIVITY] 10 - 14 November 2014

by Venkataramanan Kumar

= Progress == * TSAN support for Aarch64 (4/10) * Fix Linaro Bug 863,869 - reproduced them. Working on fixing 863 (1/10) * Misc [3/10] Emails, linaro and AMD status meetings. 1-1 with inline mangers (Mev, Ryan). 1-1 with christophe. * 11/11/2014 Leave (2/10) The task on "Debug and understand the inline differences trunk vs linaro compiler for core mark at -O3 with LTO + PGO" is on hold now. == Plan == * TSAN support for Aarch64. * Fix Linaro Bug 863 * AMD internal event on 17/11/2014.

10 years, 7 months

[Weekly] 10-14 NOV 2014

by Michael Collison

== This week == * GCC Modularization Project (4/10) - Flattening header files - gimple-streamer.h, tree-streamer.h, lto-streamer.h - Additional updates based on review: - Additional fixes based on boostrapping in contrib/config-list.mk - Boostrapped changes on all targets in contrib/config-list.mk - New changes being reviewed - Preparing patch - tree-core.h - Completed flattening - Boostrapped changes on all targets in contrib/config-list.mk * Vacation (6/10) == Next week == - Submit gimple-streamer.h, tree-streamer.h, lot-streamer.h patches - Submit tree-core.h patches - Continue flattening include files

10 years, 7 months

[ACTIVITY] 10 - 14 November 2014

by Kugan

== Progress == * Zero/sign extension elimination with widening types (5/10) - Addressing comments from the review * Improve block memory operations by GCC (TCWG-142 - 5/10) - Looked at gcc/glibc implementations - Experimented with x86_64 vs ARM and found different implementation decisions - Discussed work items == Plan == * Continue with improve block memory operations by GCC. * Continue with Zero/sign extension.

10 years, 7 months

[ACTIVITY] 10 - 14 November 2014

by Will Newton

== Progress == * Building an ILP32 toolchain for AArch64 (5/10, TCWG-559) * Investigate ARM port of lld (3/10) * Email, meetings, etc. (2/10) == Issues == * None == Plan == * Further work on ILP32 toolchain * LLD -- Will Newton Toolchain Working Group, Linaro

10 years, 7 months

[ACTIVITY] Week 46

by Renato Golin

== Progress == Lab move == Plan == Lab move

10 years, 7 months

[ACTIVITY] 10-14 November 2014

by Christophe Lyon

1 day off (2/10) == Progress == * Linaro GCC 4.8 - updated branch merge, to include the latest errata-related backport - added Michael's backport for bug #534. * GCC trunk/4.9 cross-validation (2/10) - updated vbic/vorn tests patch - trying to track down cause of spurious 'interrupted system call' errors in the ST Compute Farm * AArch64 sanitizer (1/10) - After discussing with Arnd, the kernel patch causing trouble to libsanitizer should also be backported to stable kernel branches. This makes a compiler test based on kernel version impracticable. - Shared this feedback with sanitizer maintainers, got no feedback. - libsanitizer maintainers have updated GCC's snapshot with a more recent version: - GCC trunk now requires updated kernel headers for aarch64 - reported regressions when the compiler generates Thumb code (incomplete backtrace) * Neon intrinsics tests (2/10) - submitted a series of 9 new tests. - looking at vldX bugs on aarch64_be, along with ARM's incomplete patches. * cbuild2 - no progress * Misc (3/10) - calls, meetings, support == Next == * AArch64 sanitizers * Neon intrinsics * cbuild2 (improve backport-test and tcwgweb)

10 years, 7 months

[ANNOUNCE] Linaro GCC 4.9 and 4.8 2014.11 released

by Yvan Roux

The Linaro Toolchain Working Group (TCWG) is pleased to announce the 2014.11 stable release of both Linaro GCC 4.9 and Linaro GCC 4.8 source packages. With the imminent release of ARMv8 hardware and the recent release of the GCC 4.9 compiler the Linaro TCWG will be focusing on stabilization and performance of the compiler as the FSF GCC compiler. The Linaro TCWG provides stable[1] quarterly releases and monthly engineering[2] releases. Linaro GCC 4.9 2014.11 is the eighth Linaro GCC source package release and second stable one in the 4.9 series. It is based on FSF GCC4.9.3-pre+svn216979 and includes performance improvements and bug fixes. Interesting changes in this GCC source package release include: * Updates to GCC 4.9.3-pre+svn216979 * Backport of [AArch64] Fix ILP32 ld.so * Add new Linaro release macros : __LINARO_RELEASE__ and __LINARO_SPIN__ Linaro GCC 4.8 2014.11 is the fifteenth release in the 4.8 series and second one since entering maintenance. Based off the latest GCC 4.8.4-pre+svn217270 release, it includes performance improvements and bug fixes. Interesting changes in this GCC source package release include: * Linaro bugzilla PR fixed : #307, #534 * Updates to GCC 4.8.4-pre+svn217270 * Add new Linaro release macros : __LINARO_RELEASE__ and __LINARO_SPIN__ Feedback and Support Subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro development. ** Linaro Toolchain Development "mailing list": http://lists.linaro.org/mailman/listinfo/linaro-toolchain ** Linaro Toolchain IRC channel on irc.freenode.net at @#linaro-tcwg@ * Bug reports should be filed in bugzilla against GCC product: http://bugs.linaro.org/enter_bug.cgi?product=GCC * Questions? "ask Linaro": http://ask.linaro.org/. * Interested in commercial support? inquire at "Linaro support":mailto: support(a)linaro.org [1] Stable source package releases are defined as releases where the full Linaro Toolchain validation plan is executed. [2] Engineering source package releases are defined as releases where the compiler is only put through unit-testing and full validation is not performed.

10 years, 7 months

[Question] Should gdb client query FP registers even if gdb server does not report having org.gnu.gdb.aarch64.fpu feature?

by Qu, Strong

Hello, We have implemented gdb server in one of our project and we are using Linaro aarch64-none-elf-gdb.exe as gdb client. Our gdb server will response to packet 'qXfer:features:read:target.xml:0,fff' with a xml file which only claims feature 'org.gnu.gdb.aarch64.core'. However, when I issue 'info reg' command with the gdb client, it actually sends out a packet '$p42#d6', which is trying to read fpsr if I understand correctly. Is this an expected behavior or not? I just want to figure out whether our gdb server send some bad info to the gdb client and made the client thinks FP registers are valid. I hope I made my question clear and I'm really appreciate if anybody can help us on this again. Thanks, Strong

10 years, 7 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain