- linaro-toolchain - lists.linaro.org

by Asa Sandahl

* Working on getting everything in place for cross-compiling Firefox for ARM. Trying to understand how the configuration script and make file works. * Working on a test that will run Sunspider and extract the results. The challenging part is that results are only presented on the page, not e.g. written to stdout or to file. My approach to create an html file, embed the page with the test in an iframe, and read out the results when the test is done. * Running SPEC2K on the Snowball board. An updated kernel solved the issue with great variations in the test results. Some tests results look a bit strange, so I will look at what those tests do to see what part of the system is stressed. Best Regards Åsa

13 years, 11 months

1
0
0 0

[ACTIVITY] September 18-22

by Ira Rosen

Hi, * widening shifts patch - submitted upstream * change default vector size patch - submitted to linaro-gcc * automatic choice of vector size for basic block vectorization - testing * vectorizer bug fixes Next week we have New Year holiday on Wednesday (half day) and Thursday. Ira

13 years, 11 months

1
0
0 0

Linaro GCC 4.6 and 4.5 2011.09 released

by Michael Hope

The Linaro Toolchain Working Group is pleased to announce the 2011.09 release of both Linaro GCC 4.6 and Linaro GCC 4.5. Linaro GCC 4.6 2011.09-1 is the seventh release in the 4.6 series. Based off the latest GCC 4.6.1+svn178681, it contains a range of vectoriser and core performance improvements as well as fixing a number of bugs. Interesting changes include: * Updates to 4.6.1+svn178681 * Improves performance by making better use of conditional compares * Improves performance by properly scheduling widening multiplies * Improves size and speed by improving constant generation in Thumb-2 * Implements support for widening multiples in toe core * Improves vectorised code by reducing the over-promotion of intermediates * Improves performance by reducing redundant moves between VFP and ARM * Finishes off supporting the Android team in integrating Linaro GCC Fixes: * LP: #823548 Can't use -flto with skia * LP: #823711 libvirt version 0.9.2-4ubuntu8 failed to build on armel * LP: #827990 internal compiler error: in decode_addr_const, at varasm.c:2632 * LP: #836401 ICE on a | (b << negative-constant) * LP: #838994 ICE building perl w/ -marm * LP: #843775 ICE optimizing widening multiply-and-accumulate Linaro GCC 4.5 2011.09 is the fourteenth release in the 4.5 series. Based off the latest GCC 4.5.3+svn178560, this is a maintenance focused release. Interesting changes in 4.5 include: * Updates to 4.5.3+svn178560 Fixes: * LP: #823711 libvirt version 0.9.2-4ubuntu8 failed to build on armel The source tarballs are available from: https://launchpad.net/gcc-linaro/+milestone/4.6-2011.09 https://launchpad.net/gcc-linaro/+milestone/4.5-2011.09 Downloads are available from the Linaro GCC page on Launchpad: https://launchpad.net/gcc-linaro More information on the features and issues are available from the release page: https://launchpad.net/gcc-linaro/4.6/4.6-2011.09 https://launchpad.net/gcc-linaro/4.5/4.5-2011.09 Mailing list: http://lists.linaro.org/mailman/listinfo/linaro-toolchain Bugs: https://bugs.launchpad.net/gcc-linaro/ Questions? https://ask.linaro.org/ Interested in commercial support? inquire at support(a)linaro.org -- Michael

13 years, 11 months

3
4
0 0

Bootstrapping GCC in PGO, LTO, and SMS modes

by Michael Hope

I tried to bootstrap current GCC trunk and our latest gcc-linaro-4.6 in profile guided, link time optimisation, and SMS modes. The results are here: https://wiki.linaro.org/MichaelHope/Sandbox/PGOLTOSMSStatus1 Short story: you can't bootstrap in LTO or PGO on ARM as they run out of memory. i686 LTO is broken on trunk and gcc-linaro-4.6. SMS is fine in general. I'll run these once a week and keep an eye on them. A -fwhopr instead of -flto may help on ARM. I don't know why the PGO build runs out of memory. -- Michael

13 years, 11 months

1
0
0 0

libav IDCT speed tests

by Michael Hope

Måns pointed me at the IDCT throughput test that's included with libav. I've written up a page on how to build and run it at: https://wiki.linaro.org/MichaelHope/Sandbox/LibAvDCT Included are results with and without the vectoriser. In all cases the vectoriser improves things, including increasing the SIMPLE-C version by 11 % and the peak by 17 %. The coefficient of variance is low so the results are consistent. I haven't investigated the benchmark itself to see if its valid - we could be vectorising the loop overhead instead of the IDCT itself. -- Michael

13 years, 11 months

1
0
0 0

Implicit-it upstream discussion.

by Andrew Stubbs

Hi Michael, Here's the gcc-patches@ discussion you asked for: http://gcc.gnu.org/ml/gcc-patches/2010-07/msg01339.html http://gcc.gnu.org/ml/gcc-patches/2010-07/msg01351.html http://gcc.gnu.org/ml/gcc-patches/2010-07/msg01353.html http://gcc.gnu.org/ml/gcc-patches/2010-07/msg01354.html http://gcc.gnu.org/ml/gcc-patches/2010-07/msg01355.html http://gcc.gnu.org/ml/gcc-patches/2010-07/msg01356.html http://gcc.gnu.org/ml/gcc-patches/2010-07/msg01357.html Andrew

13 years, 11 months

2
1
0 0

Re: eglibc and fun with config.sub

by Michael K. Edwards

Please coordinate with Jon Masters at RedHat/Fedora and Adam Conrad at Ubuntu/Debian on this. (Cc'ing the cross-distro list, through which the recent ARM summit at Linux Plumbers was organized.) Cheers, - Michael On Sep 16, 2011 8:41 AM, "David Gilbert" <david.gilbert(a)linaro.org> wrote: > OK, so we seem to have agreement here that what we want is autodetect > for eglibc and > forget about the triplet; well technically that probably makes my life > easier, and I don't > think it's too hard a sell. > > Dave > > _______________________________________________ > linaro-toolchain mailing list > linaro-toolchain(a)lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-toolchain

13 years, 11 months

3
2
0 0

[ACTIVITY] 12th - 17th September

by Andrew Stubbs

* Linaro GCC Spun 4.5 and 4.6 2011.09 GCC release tarballs. Uploaded them to Michael's server, and kicked off the tests. Continued work on my new constant optimization experiments. I now have it tracking all the constants and am looking at how to detect the optimization opportunities. So far it only calculates how exprensive it would be to generate a value by adding to an existing constant, which is a start at least. I'm having difficulties detecting whether changing an insn will make it's parent (dependency-wise) obsolete, or not (and therefore whether to count its costs - there's no problem for instructions that overwrite an entire register, but ones that write to portions of registers (such as MOVT) make more complex dependency chains, and the def-use chains don't seem to be sorted into the order of use. * Other Half day vacation on Thursday.

13 years, 11 months

1
0
0 0

gcc segfaults when building v8 (nodejs)

by AJ ONeal

Using the Linaro prebuilt package from a few days ago I got a segfault in gcc that is not manifest in a version from a few months earlier. Details are here: https://gist.github.com/1223209 A small snippet: g++ -o obj/release/jsregexp.o -c -fno-rtti -fno-exceptions -Wall -W -Wno-unused-parameter -Wnon-virtual-dtor -Wno-abi -pedantic -mfloat-abi=softfp -O3 -fomit-frame-pointer -fdata-sections -ffunction-sections -ansi -fno-strict-aliasing -DCAN_USE_VFP_INSTRUCTIONS -DUSE_EABI_HARDFLOAT=0 -DV8_TARGET_ARCH_ARM -DENABLE_DEBUGGER_SUPPORT -I/home/user/Code/node/deps/v8/src /home/user/Code/node/deps/v8/src/jsregexp.cc g++: Internal error: Segmentation fault (program as) Please submit a full bug report. See <file:///usr/share/doc/gcc-4.5/README.Bugs> for instructions. scons: *** [obj/release/jsregexp.o] Error 1 scons: building terminated because of errors. Waf: Leaving directory `/home/user/Code/node/out' Build failed: -> task failed (err #2): {task: libv8.a SConstruct -> libv8.a} make: *** [program] Error 1 user@linaro-developer:~/Code/node$ uname -a Linux linaro-developer 3.0.0-1004-linaro-omap #5~ppa~natty-Ubuntu SMP PREEMPT Mon Aug 22 08:44:20 UTC 2011 armv7l armv7l armv7l GNU/Linux user@linaro-developer:~/Code/node$ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/arm-linux-gnueabi/gcc/arm-linux-gnueabi/4.5.2/lto-wrapper Target: arm-linux-gnueabi Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.5.2-8ubuntu4' --with-bugurl=file:///usr/share/doc/gcc-4.5/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.5 --enable-shared --enable-multiarch --with-multiarch-defaults=arm-linux-gnueabi --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib/arm-linux-gnueabi --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.5 --libdir=/usr/lib/arm-linux-gnueabi --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-plugin --enable-gold --enable-ld=default --with-plugin-ld=ld.gold --enable-objc-gc --disable-sjlj-exceptions --with-arch=armv7-a --with-float=softfp --with-fpu=vfpv3-d16 --with-mode=thumb --disable-werror --enable-checking=release --build=arm-linux-gnueabi --host=arm-linux-gnueabi --target=arm-linux-gnueabi Thread model: posix gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu4) AJ ONeal

13 years, 11 months

2
1
0 0

[ACTIVITY] Weekly status

by Revital Eres

* Added testcases to Richard's micro benchmarks taken from libav. * Discussed with Ayal the new version of the patch to support instructions with REG_INC_NOTE in SMS which causes bootstrap failure. I intend to debug the bootstrap failure in order to find the cause for it. (http://gcc.gnu.org/ml/gcc-patches/2011-08/msg01216.html)

13 years, 11 months

1
0
0 0

[ACTIVITY] 2011-09-16

by David Gilbert

== String routines == * Tidying up bits of cortex strings for the release process * Nailing down the behaviour of config.sub and the config systems in gcc, binutils and eglibc == Other == * A discussion on synchronisation primitives on various CPUs that started on the gcc list - looking at http://www.cl.cam.ac.uk/~pes20/cpp/cpp0xmappings.html - pointing out the 64bit instructions - asking why they used isb's when neither the kernel or gcc use them (answer the DMBs should be fine as well, but there is some debate over which is quicker, oh and DMBs are converted to slower dsb's on most A9s due to an errata). * Looking for docs on the non-core bits of current SoCs * Extracting some denbench stats from a few months back for Ramana About a day of non-Linaro IBM stuff. Dave

13 years, 11 months

1
0
0 0

[ACTIVITY] report week 37

by Peter Maydell

RAG: Red: Amber: Green: NB: since qemu-linaro releases demonstrably go out on schedule every month I'm dropping them from the milestone tables in these reports, in favour of blueprint completion dates (usually they'll be planned for dates coinciding with a qemu-linaro release). Current Milestones: || || Planned || Estimate || Actual || ||add-omap3-networking || 2011-10-13 || 2011-10-13 || || ||a15-systemmode-planning || 2011-10-13 || 2011-10-13 || || ||a15-usermode-support || 2011-11-10 || 2011-11-10 || || ||upstream-omap3-cleanup || 2011-11-10 || 2011-11-10 || || Historical Milestones: ||qemu-linaro 2011-04 || 2011-04-21 || 2011-04-21 || 2011-04-21 || ||qemu-linaro 2011-05 || 2011-05-19 || 2011-05-19 || n/a || ||close out 1105 blueprints || 2011-05-28 || 2011-05-28 || 2011-05-19 || ||complete 1111 planning || 2011-05-28 || 2011-05-28 || 2011-05-27 || ||qemu-linaro-2011-06 || 2011-06-16 || 2011-06-16 || 2011-06-16 || ||qemu-linaro-2011-07 || 2011-07-21 || 2011-07-21 || 2011-07-21 || ||qemu-linaro 2011-08 || 2011-08-18 || 2011-08-18 || 2011-08-18 || ||qemu-linaro 2011-09 || 2011-09-15 || 2011-09-15 || 2011-09-15 || == linaro-qemu-11.11 == * completed this month's release == add-omap3-networking == * investigated why qemu's usb-net model didn't work on the beagle; this was due to a bug in the usb-ohci controller model; patches sent upstream. Fix will go into qemu-linaro 2011-10. == a15-system-mode-planning == * wrote up options and my suggestion on the wiki: https://wiki.linaro.org/PeterMaydell/QemuA15 * just need to discuss with Michael and turn this into a roadmap entry == a15-usermode-support == * complete but untested implementation of UDIV and SDIV * fused multiply-accumulate: implemented decode, and the special-cases parts of the softfloat implementation (NaN, inf, etc); the difficult bit of actually implementing the operation remains == other == * meetings: toolchain, pdsw doughnuts, AFDS Current qemu patch status is tracked here: https://wiki.linaro.org/PeterMaydell/QemuPatchStatus Absences (to end of year): Sep 19, Sep 29-Oct 07, Oct 17, Nov 21, Dec 15-Jan 03: leave Oct 30-Nov 04: Linaro Connect Q4.11

13 years, 11 months

1
0
0 0

eglibc and fun with config.sub

by David Gilbert

As mentioned on the standup call this morning, I've been trying to get my head around the way different parts of the toolchain using the config scripts and the triplets. I'd appreciate some thoughts on what the right thing to do is, especially since there was some unease at some of the ideas. My aim here is to add an armv7 specific set of routines to the eglibc ports and get this picked up only when eglibc is built for armv7; but it's getting a bit tricky. eglibc shares with gcc and binutils a script called config.sub (that lives in a separate repository) which munges the triplet into a $basic_machine and validates it for a set of known triplets. So for example it has the (shell) pattern: arm | arm[bl]e | arme[lb] | armv[2345] | armv[345][lb] to recognise triplets of the form arm- armbe- armle- armel- armbe- armv5- armv5l- or armv5b- It also knows more obscure things such as if you're configuring for a netwinder it's an armv4l- system running linux - but frankly most of that type of thing are a decade or two out of date. Note it doesn't yet know about armv6 or armv7. eglibc builds a search path that at the moment includes a path under the 'ports' directory of the form arm/eabi/$machine where $machine is typically the first part of your triplet; however at the moment eglibc doesn't have any ARM version specific subdirectories. If I just added an ports/sysdeps/arm/eabi/armv7 directory it wouldn't use it because it searches in arm/eabi/arm if configured with the triplet arm-linux-gnueabi or --with-cpu sets $submachine (NOT $machine) - so if you pass --with-cpu=armv7 it ends up searching arm/eabi/arm/armv7 if you used the triplet arm-linux-gnueabi. If you had a triplet like armel then I think it would be searching arm/eabi/armel/armv7 So my original patch ( http://old.nabble.com/-ARM--architecture-specific-subdirectories,-optimised… ) did the following: * Modified the paths searched to be arm/eabi (rather than arm/eabi/$machine) * If $submachine hadn't been set by --with-cpu then autodetect it from gcc's #defines which meant that it ignored the start of the triplet and let you specify --with-cpu=armv7 After some discussion with Joseph Myers, he's convinced me that isn't what eglibc is expecting (see later in the thread linked above); what it should be doing is that $machine should be armv7 and $submachine should be used if we wanted say a cortex-a8 or cortext-a9 specific version. My current patch: * adds armv6 and armv7 to config.sub * adds arm/eabi/armv7 and arm/eabi/armv6t2 and one assembler routine in there. * If $machine is just 'arm' then it autodetects from gcc's #defines * else if $machine is armv.... then that's still $machine So if you use: a triplet like arm-linux-gnueabi it looks at gcc and if that's configured for armv7-a it searches arm/eabi/armv7 a triplet like armv7-linux-gnueabi then it searches arm/eabi/armv7 irrespective of what gcc was configured for a triplet like armv7-linux-gnueabi and --with-cpu=cortex-a9 then it searches arm/eabi/armv7/cortex-a9 then arm/eabi/armv7 As far as I can tell gcc ignores the first part of the triplet, other than noting it's arm and spotting if it ends with b for big endian; (i.e. configuring gcc with armv4-linux-gnueabi and armv7-linux-gnueabi ends up with the same compiler). binutils also mostly ignores the 1st part of the triple - although is a bit of a mess with different parts parsing it differently (it seems to spot arm9e for some odd reason); as far as I can tell gold will accept armbe* for big endian where as ld takes arm*b ! If you're still reading, then the questions are: 1) Does the approach I've suggested make sense - in particular that the machine directory chosen is based either on the triplet or where the triplet doesn't specify the configuration of gcc; that's my interpretation of what Joseph is suggesting. 2) Doing (1) would seem to suggest I should give config.sub armv6t2 and some of the other complex names. Dave

13 years, 11 months

4
4
0 0

[ACTIVITY] Weekly status

by Richard Sandiford

== This week == * Reviewed patches for the release. * ...then broke the release. Tried to spin a new one. * Worked on a "real" fix for bug 850099. Now in testing. * Looked more at auto-inc-dec stuff. Saw a case that didn't behave as I expected on the A9. The A9 TRM doesn't describe what happens for post-indexed addressing, so I asked Ramana. Apparently the behaviour is expected. Once I have more info, I'll try to update the patches. * Worked on neon-highlow-extract and neon-strided-load-extract. Posted the three patches upstream. Nicely, the one I thought was going to be the most controversial actually got positive feedback from Paolo (who wrote the affected code). Richard

13 years, 11 months

1
0
0 0

[ACTIVITY] Sep 12 - Sep 16

by Ulrich Weigand

== GDB == * Completed hardware watchpoint support for gdbserver. * Tracked down watchpoint resource accounting regression on GDB mainline (not present in 7.3). * Created and published Linaro GDB 7.3-2011.09 release. Mit freundlichen Gruessen / Best Regards Ulrich Weigand -- Dr. Ulrich Weigand | Phone: +49-7031/16-3727 STSM, GNU compiler and toolchain for Linux on System z and Cell/B.E. IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter | Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen | Registergericht: Amtsgericht Stuttgart, HRB 243294

13 years, 11 months

1
0
0 0

[ACTIVITY] w37

by Asa Sandahl

* Running SPEC2K on the Snowball board. A fresh kernel with HIGHMEM enabled made it possible to run the tests. Great variations in the results indicates that something strange is going on. Turning off one of the CPU:s gives stable result (but slow), so my current guess is that the variations are caused by a known bug that makes one cpu run slower. http://igloocommunity.org/bugzilla3/show_bug.cgi?id=1 The patch for this bug was not included in my kernel. Will have another go with a kernel where the patch is included, as a background activity. * Planned and started working on the "Adding browsing benchmarks to our current set of tests"-activity. I will try to keep documentation up to date here: https://wiki.linaro.org/AsaSandahl/Sandbox/BrowsingBenchmarks Experimenting with building Firefox in different ways, so far for x86. Best Regards Åsa

13 years, 11 months

1
0
0 0

Re: [Linaro-toolchain-benchmarks] Using u-boot for perf measurements.

by Michael Hope

(bouncing to linaro-dev as it's generally interesting) On Fri, Sep 16, 2011 at 8:17 AM, Ramana Radhakrishnan <ramana.radhakrishnan(a)linaro.org> wrote: > Hi, > > I've been looking at some of the perf regressions we've been seeing > these days in an attempt to understand what's going on in these cases. > While I can use perf and get more statistics and do other things to > figure out why there are perf regressions between 2 binaries along > with perf record and report, I wonder if it is possible to use u-boot > to accurately measure what's going on. I would like to try and get the > values of the performance counters between 2 program points . > > I am aware that there are patches that are floating around that allow > users to set and reset the PMU counters by allowing user level access > to it in the kernel : while that maybe useful to some I'm not sure if > I want to take a chance with some other process getting scheduled that > ends up getting scheduled. Even if there are parts of the kernel that > save and restore PMU counters associated per process with across > context switches . I'm looking for as accurate measurements as > possible in this case and I wonder if u-boot is the best bet for this > ( in the absence of any dedicated hardware debug / trace unit) given > not all of us have one. > > > At the minimum to do this I believe we require u-boot or some start-up code to: > > * Turn on i-cache and d-cache. ( The current u-boot for panda that I > get from the linaro-uboot git repo > git://git.linaro.org/boot/u-boot-linaro-stable.git says "Warning > Caches turned off" when starting up ). Googling around I find a few > patches floating around that turn on the d-cache in August from Aneesh > at TI . We should consider getting these in at some point. > > * Looking in $(UBOOT_TOP)/examples/api I see that there are simple > printf routines and simple stand-alone applications that exist which > could be used for this purpose. The one problem with this is the fact > that u-boot appears to require use of -ffixed-r8 for it's purposes > which *might* mean we need these if we were to use API calls into > standard u-boot functions . I wonder if R8 is used in the current ARM version? There's no reason we can't cherry pick parts such as the serial I/O out into a library and make the app completely self contained. Skip all of the initialisation stuff and assume the boot loader has done it for you. > * Turn on / off speculative prefetching - I believe the kernel does > this already for a few boards, but could this be done in u-boot just > before it launches a test application ? > > * Turn on the VFP and Neon units. > > * Turn on unaligned access so that unaligned accesses are allowed in > the test applications. GCC will now move towards generating unaligned > accesses on versions of the architecture that support it, the patches > upstream have now been approved. > > * Memory map / linker scripts to make sure we are putting things in > the right places (sigh, has to be per-board). But everything goes in RAM so you have one generic linker script and a per board MEMORY definition. Similar to: http://bazaar.launchpad.net/~stm32f-dev/stm32f-dev/stm32f-startup/view/head… ...but even lighter. > We then write a set of library functions that could then look at what > performance counters are of interest to us and track them by resetting > them to 0 and making sure they haven't overflown. > > Has anyone else in the group played with u-boot before or has any > thoughts in this direction ? I am not suggesting that we do this work > right now but it sounds like an interesting thought of where we can > get to with this. My worry is that we miss turning on a feature and get results that aren't representative. That should be easy enough to check by baselineing against a Linux hosted run. We can use NFS or kermit to load the programs. u-boot has a network console which is nice when you don't have serial. This combined with an expect script (or LAVA? Paul?) should automate the whole process. -- Michael

13 years, 11 months

1
0
0 0

[ACTIVITY] weekly status

by Ken Werner

Hi, * put the sources of the libunwind android port, the patches for debuggerd and the Android test app online * documented things at: https://wiki.linaro.org/WorkingGroups/ToolChain/Outputs/LibunwindDebuggerd * noticed differences between the old (debuggerd) and the new (debuggerd+libunwind) backtraces * I'm still not sure what's going on (maybe they are adding offsets or something) * however, the backtrace that libunwind does looks sane to me Note: I'll be on vacation till October 7th. Regards Ken

13 years, 11 months

1
0
0 0

[ACTIVITY] September 11-15

by Ira Rosen

Hi, * testing widen-shifts patch on ARM * SLP improvements: - submitted a patch to allow not simple ivs in SLP - committed a patch to allow read-after-read dependencies in SLP Ira

13 years, 11 months

1
0
0 0

Linaro QEMU 2011.09 released

by Peter Maydell

The Linaro Toolchain Working Group is pleased to announce the release of Linaro QEMU 2011.09. Linaro QEMU 2011.09 is the latest monthly release of qemu-linaro. Based off upstream (trunk) QEMU, it includes a number of ARM-focused bug fixes and enhancements. New in this month's release: - linux-user mode now supports the 64 bit cmpxchg kernel helpers (only needed for applications compiled for ARMv6 or lower) - PL111 display controller now supported; this fixes a problem where BGR was interpreted as RGB on recent versatilepb kernels Plus a few other minor bug fixes and the usual round of upstream fixes and improvements. Known issues: - The beagle and beaglexm models still do not support USB networking; we intend to fix this for the 2011.10 release - There may be some problems with running multithreaded programs in linux-user mode (LP:823902) The source tarball is available at: https://launchpad.net/qemu-linaro/+milestone/2011.09 Binary builds of this qemu-linaro release are being prepared and will be available shortly for users of Ubuntu. Packages will be in the linaro-maintainers tools ppa: https://launchpad.net/~linaro-maintainers/+archive/tools/ More information on Linaro QEMU is available at: https://launchpad.net/qemu-linaro

13 years, 11 months

1
0
0 0

Linaro GDB 7.3 2011-09 released

by Ulrich Weigand

The Linaro Toolchain Working Group is pleased to announce the release of Linaro GDB 7.3. Linaro GDB 7.3 2011.09 is the second release in the 7.3 series. Based off the latest GDB 7.3, it includes a number of ARM-focused bug fixes and enhancements. This release contains: * Support for hardware breakpoints and watchpoints in gdbserver The source tarball is available at: https://launchpad.net/gdb-linaro/+milestone/7.3-2011.09 More information on Linaro GDB is available at: https://launchpad.net/gdb-linaro

13 years, 11 months

1
0
0 0

Branch is open

by Michael Hope

Hi there. The 2011.09 release has been spun and is testing up well. The 4.5 and 4.6 branches are now open so feel free to commit any approved patches. -- Michael

13 years, 11 months

1
0
0 0

arm-eabi-g++: error: unrecognized option '-avoid-version'

by Asa Sandahl

Hi! When building Android with the Linaro toolchain, I encountered this link time error when going from gcc 4.4.3 to gcc 4.6. "arm-eabi-g++: error: unrecognized option '-avoid-version'" I find several posts about people encountering the same thing for different programs. Was this option removed? Anyone know the story behind it? Regards Åsa

13 years, 11 months

2
2
0 0

Blueprints, Headline and Acceptance criteria for monthly releases

by Mounir Bsaibes

Release Management needs the list of the the blueprints that will be delivered this month. For each bp, they want a Headline and Acceptance criteria. The Headline is a statement to include in the Monthly release announcement. The acceptance criteria is a statement how to verify the work is done. I have collected this month's blueprints in the spreadsheet, please review it for accuracy. If a blueprint you are working on is missing, please add it. The Headline and Acceptance can be added into the whiteboard as follows: Headline: headline text Acceptance: acceptance text Once you add the the headline and acceptance, please modify the spreadsheet to reflect that it is done. https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0AoZqvK7R1biJdGxSc… Thanks in advance, Mounir -- Mounir Bsaibes Project Manager Follow Linaro.org: facebook.com/pages/Linaro/155974581091106 http://twitter.com/#!/linaroorg http://www.linaro.org/linaro-blog <http://www.linaro.org/linaro-blog>

13 years, 11 months

3
2
0 0

[Activity] Weekly report for w/e 2011-09-09

by Ramana Radhakrishnan

==GCC== ===Progress=== * Fixed https://bugs.launchpad.net/ubuntu/+source/gcc-4.6/+bug/838994 . Investigated Bernd's alternate patch . Will commit mine. * Looked at PR48308 for sometime whihc might be a dup of PR50313 . * Some blueprint foo. * Committed a few of the outstanding approved patches into Linaro GCC-4.6 * Patch review week * Caught up with email after vacation. === Plans === * Commit conditional compares patch. * Commit the patch for LP838994. * Investigate some of the performance issues with strlen and some of the cases with - one of the ideas is to probably try and get the specific testcases run under u-boot or as a bare-metal binary and look at dumps of various performance monitoring counters and see what's happening. * Look at BRANCH_COST and finish that up next. * Dust off patch for PR19599 . One of them them that has fallen into the cracks. * Some patch review. Meetings: * 1-1s * TCWG calls * Thumb2 performance call. Absences. * 16th Oct (pm) - LLVM developer summit - London * 31st Oct - 4th Nov - Linaro Summit Orlando - Travel booked - hotel to be booked. * 08 Nov - 11 Nov - Tentatively booked not approved. * Dec 19 - 31st Dec - Tentatively booked not approved.

13 years, 11 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain