- linaro-toolchain - lists.linaro.org

[ANNOUNCE] Linaro GCC 4.8 2013.07-1 released.

by Yvan Roux

The Linaro Toolchain Working Group announce the 2013.07-1 Linaro GCC 4.8 release. This is a respin of the 2013.07 release because of an issue with internal memcpy and -mno-unaligned-access. The source tarball is available from: https://launchpad.net/gcc-linaro/+milestone/4.8-2013.07-1 Please find the original 2013.07 announcement below. The Linaro Toolchain Working Group is pleased to announce the release of both Linaro GCC 4.8 and Linaro GCC 4.7. Linaro GCC 4.8 2013.07 is the fourth release in the 4.8 series. Based off the latest GCC 4.8.0+svn200355 release, it includes performance improvements and bug fixes. Interesting changes include: * Updates to GCC 4.8.1+svn200355 * Address Sanitizer support for ARM. * New -mrestrict-it option support. * Backport of support for further AArch64 instructions. * Backport of support for further ARMv8 AArch32 instructions. * Reverted recent changes to shrink-wrapping and tail-calls. Linaro GCC 4.7-2013.07 is the sixteenth release in the 4.7 series. Based off the latest GCC 4.7.3+svn200408 release, this is the third release after entering maintenance. Interesting changes include: * Updates to GCC 4.7.3+svn200408 The source tarballs are available from: https://launchpad.net/gcc-linaro/+milestone/4.7-2013.07 https://launchpad.net/gcc-linaro/+milestone/4.8-2013.07 Downloads are available from the Linaro GCC page on Launchpad: https://launchpad.net/gcc-linaro Mailing list: http://lists.linaro.org/mailman/listinfo/linaro-toolchain Bugs: https://bugs.launchpad.net/gcc-linaro/ Questions? http://ask.linaro.org/ Interested in commercial support? inquire at support(a)linaro.org

12 years, 5 months

1
0
0 0

[ACTIVITY] 15-19 July2013

by Venkataramanan Kumar

== Progress == Was on vacation most of the week Mon - Wed leave (Thursday half day). * Libssp support for AArch64 TCWG 23 Restarted the work. Looked at how X86 GCC generated code. Looking at per thread support for libssp and compiler support. == Plan == * Continue Libssp support for AArch64 TCWG-23 * Look at builtin return address behaviour in the absence of frame pointer. ==issues== * LTO/PGO work stopped now since libssp support priority is more.

12 years, 5 months

1
0
0 0

[ACTIVITY] Weeks 28-29

by Yvan Roux

== Issues == * None. == Progress == * Attended linaro Connect (Wk 28) * OE Launchpad bug #1200620 : [ICE while building Exynos5 kernel with current 4.8 branch] - Issue due to a bad usage of unaligned load/store in HI mode - Fix approved and committed upstream - Release respin ongoing. * Launchpad bug #1186218 : [kernel doesn't boot on Arndale/Nexus with Linaro GCC 4.8] - Discussed the issue at Connect - Waiting for a reduce testcase from the kernel team. * LRA on AArch64: - Some regressions in the testsuite - Debugging ongoing. * LRA on AArch32: - Still some issues with libgcc build in Thumb - Back on this issue. * 2013-08 4.8 release: - Backports from trunk ongoing. == Plan == * 4.8 Backports * Summer break

12 years, 5 months

1
0
0 0

[ACTIVITY] 15 - 19 July 2013

by Omair Javaid

== Progress == * Debugged gdb.mi and linux-nat code to investigate issues on arm. * Cleared pending gdb patches. * Listened to Connect sessions and key notes on youtube * Follow up on travel hick ups and UK/US visa application == Plan == * Review GDB current status and fill up JIRA with proposed future work * Windup work on gdb test suite updates and submit remaining patches. * Follow up on gdb patches * Clear/Update JIRA cards * File UK visa for meetings in September.

12 years, 5 months

1
0
0 0

[Activity] July 6-July 18

by Rob Savoye

== Progress == * Attended Connect, did presentation and other stuff. * Left Connect early to attend the Gnu Tool Cauldron. Ran BOF on testing the toolchain, attended many talks including the one on Graphite. * Worked on modularizing cbuildv2 package parsing into functions so bzr,svn,git URLs and tarball snapshots from toolchain64 work the same. * Added LLVM support to cbuildv2, Clang and the testsuites only work if built separately for now. * Reproduced build problem Viswanath was having with crosstool, Zhenqiang knew the missing package(s) that kept C++ builds from working. * Built fsf 4.7 and 4.8 as well as Linaro GCC releases for July on Panda board. * Got spec200 benchmarks working on panda, ran them for the above branches and releases. == Plans == * Help Charlie come up to speed on building GCC. * Run more benchmarks on the above branches and do graphs on performance. * See why for me on a panda, all the tests fail with make check. * Find time to work on cbuild2 so Charlie can beta test it sometime soon. - rob -

12 years, 5 months

1
0
0 0

[ACTIVITY] Week 29

by Zhenqiang Chen

== Issues == * None == Progress == * Enable multi-arch for Linaro aarch64-linux-gnu build. - Configure gcc with --enable-multiarch. - Backport eglibc patches for rtlddir. - Configure eglibc to set libdir, slibdir and rtlddir. * Follow up the patch for pr57637. * Reassociate X == CST1 || X == CST2 if popcount (CST2 - CST1) == 1 into ((X - CST1) & ~(CST2 - CST1)) == 0. - Test is ongoing. * Rebase conditional compare changes to trunk. == Leave == * July 17. == Plan == * Send out the conditional compare changes for Linaro internal review.

12 years, 5 months

1
0
0 0

[ACTIVITY] Week 29

by Renato Golin

== Progress == Short week (3 days) * Divmod - Finished most of the work, patch upstream (r186390) - Trying to lower remainder as divmod without sacrificing the div+mod merge during legalization * Buildbots - One panda fails even at 920MHz, replaced with a new one - Using decent power supplies now, should work a whole week - Lab config is messed up, need to start from scratch - Failed at 920MHz with decent power supply - Giving up on Pandas as buildbots... * Background - Not many code reviews last two weeks, as Connect and the Pandas took most of my spare time - Test-suite's Lencod bug fixed upstream, no more need of dirty hacks on stack offset calculation == Plan == * Continue on divmod lowering, finding a way to merge Custom with Expand lowering, so not to break the div+rem merge during legalization, but still lower divmod as Custom. 64-bit types still use them. * Study cross-compilation issues in Clang and LLVM, prepare a document on how it works (or not), and what paths we can take to make it better in the short/medium term. * Follow up on Phoronix results and CBuild2 benchmarks, time allowing

12 years, 5 months

1
0
0 0

[ACTIVITY] Week 29

by Will Newton

== Progress == * Investigating glibc stack guard support * Developed initial patches * Raised ABI issue * More malloc work * Integrated tcmalloc into benchmark framework * Improved benchmark repeatability * Added Python benchmark script and graphing script * Respin and commit gdb TLS testsuite patch (my gdb patch queue now empty) * Committed two of Omair's gdb patches == Issues == * None. == Plan == * Produce some malloc benchmark graphs * Progress the stack guard work * Start writing some malloc code -- Will Newton Toolchain Working Group, Linaro

12 years, 5 months

1
0
0 0

[ACTIVITY] report week 28, 29

by Peter Maydell

Progress: * attended Linaro Connect (wk 28) * sent pull requests for target-arm/arm-devs queues * resent virtio-mmio patchset; this is now ready for commit and I will send a pullreq with it in next week * finished off a cleanup of linux-user to remove the support for configuring targets without threading support * resorted todo list against cards * started on getting v7 mach-virt into shape for upstreaming -- PMM

12 years, 5 months

1
0
0 0

Support for ARMV5te

by Ratheendran R

Hi All, I am new to linaro. so would like to know more about linaro. Is linero alternative to yocto project. does the tool chain support armv5te based SOC. Ratheendran

12 years, 5 months

4
3
0 0

Overheating Pandas

by Renato Golin

Hi Folks, I'm running two buildbots here at home and am getting consistent failures from the Pandas because of overheating. I've set up a monitor that will tell me the current CPU temperature and the allowed maximum, and when the bot passes 90%, it shuts itself off. The problem is that I'm running with heat-sinks and the boards are on top of three fans, so there really isn't much more I can do to solve this problem. I personally think this is a hardware problem, since everything is in the same die, CPU, GPU and RAM, and the physical dimensions of the chip are quite small. I remember when Intel started overheating (around 486DX66) and the die was huge (more head dissipation), plus RAM and GPU were separate, and it still needed a hefty heat-sink. It's true that gates are far smaller today, but it's not true that a dual core 1.3GHz + GPU + RAM will produce less heat on a small die than a 66KHz CPU on a huge die, so why anyone think it's a good idea to release a 1+GHz chip without *any* form of heat dissipation is beyond my comprehension. Manufacturers only got away with it, so far, because people rarely use 100% of the CPU power for extended periods of time, because ARM devices end up as set-top boxes, mobile phones and tablets. However, even those devices will heat up when playing 2 h films or games, and they do have some form of heat sink. We, at the toolchain group, make things worse by using 100% CPU, 24 / 7, something that Panda boards, or Arndales were not designed to do. However, with ARM moving into the server space, their designs will have to be re-thought, and what a better place than Linaro for making sure we get it right? For the time being, I believe we *must* have air conditioning in the Lab all the time, and we *must* have heat-sinks on every board, and we *must* monitor the CPU temperature of the boards, at least until we're comfortable that they're not failing all the time. Can we make a temperature monitor (like the one attached) a default feature on Linaro Ubuntu distributions? We could dump that info to the syslog/dmesg whenever it crosses the (say) 75% threshold, and report more often when it crosses the 95%, possibly dumping the processe(s) that are consuming more CPU at the time, to enable post-mortem debugging. cheers, --renato As a side note, the quad-A9 ODroid does ship with a massive heat-sink, which also serves as a fancy case. Quite clever, really.

12 years, 5 months

9
35
0 0

[SPAM] $99 A9 desktop

by Renato Golin

http://arstechnica.com/information-technology/2013/07/99-arm-based-pc-runs-… + Quad-core-A9 @ 1.2GHz + 4GB RAM + 512GB SDD + 2 x GBit Ethernet + <8W total power http://utilite-computer.com/web/utilite-specifications The complete system will be a lot more than $99, but still, I don't think it'll be more than $500. Maybe, this will be more stable than Panda boards for toolchain testing? cheers, --renato

12 years, 5 months

2
2
0 0

How to make gcc generate optimized code for statically linked TLS

by Vitali Sokhin

Hello, I use gcc-linaro-aarch64-linux-gnu-4.8 to compile my C code with thread-local variables. Here is an example of my C code: __thread u32 threadedVar; void test(void) { threadedVar = 0xDEAD; } gcc produces the following assembly to access my threaded variable: threadedVar = 0xDEAD; 72b0: d00000c0 adrp x0, 21000 72b4: f945ac00 ldr x0, [x0,#2904] 72b8: d503201f nop 72bc: d503201f nop 72c0: d53bd041 mrs x1, tpidr_el0 72c4: 529bd5a2 movz w2, #0xdead 72c8: b8206822 str w2, [x1,x0] This assembly fits dynamically linked code, but in my case I have statically linked application that does not load any additional modules. Since I have exactly one TLS block containing all thread-local variable gcc should be able to calculate the offset at link time. Can I make gcc to produce the following assembly ? threadedVar = 0xDEAD; 72c0: d53bd041 mrs x1, tpidr_el0 72c4: 529bd5a2 movz w2, #0xdead 72c8: b8206822 str w2, [x1,#offset_to_threadedVar] Thank you, Vitali

12 years, 5 months

2
2
0 0

How to make gcc generate optimized code for statically linked TLS

by Vitali Sokhin

Hello, I use gcc-linaro-aarch64-linux-gnu-4.8 to compile my C code with thread-local variables. Here is an example of my C code: __thread u32 threadedVar; void test(void) { threadedVar = 0xDEAD; } gcc produces the following assembly to access my threaded variable: threadedVar = 0xDEAD; 72b0: d00000c0 adrp x0, 21000 72b4: f945ac00 ldr x0, [x0,#2904] 72b8: d503201f nop 72bc: d503201f nop 72c0: d53bd041 mrs x1, tpidr_el0 72c4: 529bd5a2 movz w2, #0xdead 72c8: b8206822 str w2, [x1,x0] This assembly fits dynamically linked code, but in my case I have statically linked application that does not load any additional modules. Since I have exactly one TLS block containing all thread-local variable gcc should be able to calculate the offset at link time. Can I make gcc to produce the following assembly ? threadedVar = 0xDEAD; 72c0: d53bd041 mrs x1, tpidr_el0 72c4: 529bd5a2 movz w2, #0xdead 72c8: b8206822 str w2, [x1,#offset_to_threadedVar] Thank you, Vitali

12 years, 5 months

1
0
0 0

[ANNOUNCE] Linaro GCC 4.8 and 4.7 2013.07 released

by Christophe Lyon

The Linaro Toolchain Working Group is pleased to announce the release of both Linaro GCC 4.8 and Linaro GCC 4.7. Linaro GCC 4.8 2013.07 is the fourth release in the 4.8 series. Based off the latest GCC 4.8.0+svn200355 release, it includes performance improvements and bug fixes. Interesting changes include: * Updates to GCC 4.8.0+svn200355 * Address Sanitizer support for ARM. * New -mrestrict-it option support. * Backport of support for further AArch64 instructions. * Backport of support for further ARMv8 AArch32 instructions. * Reverted recent changes to shrink-wrapping and tail-calls. Linaro GCC 4.7-2013.07 is the sixteenth release in the 4.7 series. Based off the latest GCC 4.7.3+svn200408 release, this is the third release after entering maintenance. Interesting changes include: * Updates to GCC 4.7.3+svn200408 The source tarballs are available from: https://launchpad.net/gcc-linaro/+milestone/4.7-2013.07 https://launchpad.net/gcc-linaro/+milestone/4.8-2013.07 Downloads are available from the Linaro GCC page on Launchpad: https://launchpad.net/gcc-linaro Mailing list: http://lists.linaro.org/mailman/listinfo/linaro-toolchain Bugs: https://bugs.launchpad.net/gcc-linaro/ Questions? http://ask.linaro.org/ Interested in commercial support? inquire at support(a)linaro.org

12 years, 5 months

1
1
0 0

Fwd: Please help: Linaro GDB 7.6-2013.05 Issue

by 常桓

Hi Linaro toolchain team, I compiled linaro-toolchain 2013.06 by myself on fedora 18 x86_64, everything works fine except GDB. The error message is "Im sorry, Dave, I can't do that. Symbol format `elf32-littlearm' unknown'." I searched on google, and leads me to the page https://bugs.launchpad.net/linaro-toolchain-binaries/+bug/918937 I configured linaro-toolchain to build a native gdb for arm platform, both native gdb and cross-gdb can't work, they report the same error message. Is there any way I can get the patch? Please help me on this! Thank you very much! Yupeng Chang July 05, 2013

12 years, 5 months

2
1
0 0

Re: Please help: Linaro GDB 7.6-2013.05 Issue

by 常桓

Hi Michael, I have fixed this issue. I think there is a bug in crosstool-ng-1.13.1-2013.06. In crosstool-ng-1.13.1-2013.06/contrib/linaro/patches/gdb/linaro-7.6-2013.05, there is a patch libintl-as-lib.patch, which adds -lintl to LDFLAGS of gdb, however, in the 300-gdb.sh, --without-included-gettext is used, this option makes libintl inside gdb quit building, in this case, when checking ELF support in BFD, -lintl cannot be found, this leads to fail. In eglibc-2.17, intl lib is included in libc, --without-included-gettext is reasonable to apply to gdb, which means libintl-as-lib.patch is no longer needed, because this patch adds an option which will be no longer needed for building gdb with eglibc-2.17 After I removed the patch, every thing works fine now, in gdb/config.log, checking ELF support in BFD reports OK now. Yupeng Chang July 06 2013 On 6 July 2013 03:21, Michael Hope <michaelh(a)juju.net.nz> wrote: > Hi there. I'm afraid I'm not working on gdb these days but it sounds like > a configuration error. I suggest asking on > linaro-toolchain(a)lists.linaro.org as they should be able to help. > > -- Michael > On Jul 5, 2013 8:03 PM, "常桓" <changyp6(a)gmail.com> wrote: > >> Hi Michael, >> Sorry for bothering you about a GDB issue. >> I compiled linaro-toolchain 2013.06 by myself on fedora 18 x86_64, >> everything works fine except GDB. >> The error message is "Im sorry, Dave, I can't do that. Symbol format >> `elf32-littlearm' unknown'." >> I searched on google, and leads me to the page >> https://bugs.launchpad.net/linaro-toolchain-binaries/+bug/918937 >> >> On that page, you posted this is fixed, could you show me the fix? >> >> I configured linaro-toolchain to build a native gdb for arm platform, >> both native gdb and cross-gdb can't work, they report the same error >> message. >> >> Please help me on this! >> >> Thank you very much! >> >> Yupeng Chang >> July 05, 2013 >> >> >> >>

12 years, 5 months

1
0
0 0

[ACTIVITY] 1-5 July 2013

by Christophe Lyon

== Progress == * 2013.07 release preparation: * remaining backports * reverted 2 sets of patches from 2013.06 * started release process * Worked on setting up an internal build + validation to monitor FSF trunk on ARM * Internal support == Next == * All week at Connect

12 years, 5 months

1
0
0 0

[ACTIVITY] Week 27

by Will Newton

== Progress == * 4 day week (leave on Thursday) * Pushed memcpy improvement to newlib. * Found and fixed ARM IFUNC issue in glibc. * memcpy merged into bionic but not yet used (see gerrit review). * Pinged and applied gdb testsuite patch, only one left to apply. * More work on malloc benchmarking. * Preparation for Connect. == Issues == * None. == Plan == * Connect all week -- Will Newton Toolchain Working Group, Linaro

12 years, 5 months

1
0
0 0

[ACTIVITY] Week 27

by Renato Golin

== Progress == * Buildbots - Prepared buildbot images, tested, setup is very quick and efficient - Set up local buildmaster, two buildslaves doing self-hosting tests - Each slave took 20 minutes setup time, including flashing SDCard - Failures after a few hours running at 100% @ 1.2GHz @ < 26C - Reducing to 920MHz does fix the problem, but this is not a solution - Leaving the two pandas alive during Connect in hope they won't fail * LNT Lencod - Following up on Lencod stack corruption, we're closer to a solution * Dibmod - Didn't have much time to look at it properly, but my solution was over simplified - Will probably only look at it better after Connect * Chromebook - Had to re-install Ubuntu on it, using Raring (Saucy didn't work) - Glad all my data is in the external hard-drive * Others - Added a doc about platform-specific tests that usually break the bots http://llvm.org/docs/TestingGuide.html#platform-specific-tests - LLVMLinux meeting, cross-compilation with Clang is almost impossible - Haven't been able to review many patches, thanks to Tim, they kept going! == Plan == * Connect whole next week == After Connect == * Finish implementation AEABI divmod/udivmod calls * Check why Phoronix result pages are not working * Put self-hosting bots back on 920MHz mode in the Lab

12 years, 5 months

1
0
0 0

[ACTIVITY] report week 26

by Peter Maydell

Progress: * misc: ** went through "aarch64 preparation" patchset (originally Alex's, then modified by John), fixed a lot of issues/nits, and sent out an updated version; this is now I think upstreamable-quality except that it doesn't provide anything useful on its own. ** looked at the VirtualOpenSystems patchset for v8 KVM support in QEMU; needs to be reconciled with John's work in the same area. ** Mans' LDA/STL patches now queued in target-arm.next to go upstream ** preparation for Connect Plans: * mach-virt -- PMM

12 years, 5 months

1
0
0 0

[ACTIVITY] Week 27

by Zhenqiang Chen

== Issues == * None == Progress == * Investigate library dir issue in aarch64-linux-gnu release. - Crosstool-ng should not link lib64 to lib. - Eglibc used in Linaro release is too old. No configure to change lib to lib64. - Runtime tarball should not assume multiarch (aarch64 gcc does not support it yet). - When creating runtime tarball, use lib or lib64 bases on the TARGET. * Fix misc issues in local conditional compare changes. * Investigate how to optimize "c == '+' || c == '-'". == Plan == * LCE13: July 8-12.

12 years, 5 months

1
0
0 0

[ACTIVITY] 24-28 June 2013

by Christophe Lyon

== Progress == * Short week (3 days off sick) * Aarch64 frame growing downward: sent patch * A few merges on Rob's behalf after approval by Yvan * Prepared one more merge request * Prepared for Connect * Internal support == Next == * Handle remaining backports for 4.8 release * Disable peeling: resume work

12 years, 5 months

1
0
0 0

[ACTIVITY] Week 26

by Yvan Roux

== Issues == * None. == Progress == * OE Launchpad bug #1192953 : [g++ compilation terminated with error on Linaro-openembedded lamp image] - Doko submitted a patch for that issue one year ago - Mailing list pinged * Launchpad bug #1186218 : [kernel doesn't boot on Arndale/Nexus with Linaro GCC 4.8] - Reproduced the build locally - Need to have access to some hardware for further investigations * LRA on ARM and AArch64: - Fixed the issue, compiler now bootstrap - Testing on-going before submission * 2013-07 release: - merge reviews * LCE13: - Connect registration done - flight and hotel booked. == Plan == * Merge review and release preparation * LRA

12 years, 5 months

1
0
0 0

[ACTIVITY] 24 - 28 June 2013

by Omair Javaid

== Progress == * Re-wrote gdb.dwarf2/dw2-error.exp and gdb.dwarf2/clztest.exp for arm. * Investigated catch syscall patch in gdb patches to narrow down changes required for arm. * Continued with gathering documentation for future visas. == Plan == * Test and fix failures due to optimization code in gdb.dwarf2/clztest.exp for arm. * Figure out a way to generate arm assembly for dwarf2/fission* gdb tests using gcc. * Further investigation arm requirements by going through catch syscall patch for gdb on x86. * Work with James to start UK and US visas for future visits.

12 years, 5 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain