Konstantinos, Loïc, and I talked last night about multiarch. Linaro
want multiarch and will use it in all our products and hence need to
get it upstream. There's another meeting in a week to figure out
what's next.
I've written a page on the uses, issues, and history at:
https://wiki.linaro.org/MichaelHope/Sandbox/MultiarchNotes
Please edit and add and correct things. The page isn't Linaro's
position but we need to have answers for the arguments.
I see no particular blockers especially if we separate the concerns.
-- Michael
I've added a new job called 'porter' which reserves the first tcpanda
that comes free. This can be used to reproduce a bug or benchmark
result against an existing binary build.
For example, say you want to see if a fault exists on recent trunk:
* Go to http://ex.seabright.co.nz/helpers/buildlog/gcc-4.8
* See the last successful ARM build was gcc-4.8~svn185503
* Go to http://ex.seabright.co.nz/helpers/scheduler/spawn
* Spawn a job called 'porter' into the a9-builder queue
* Keep polling http://ex.seabright.co.nz/helpers/scheduler until a
board shows as 'porter/ready'
* Log into the board using ssh cbuild(a)board.v
* Change to /scratch/cbuild/slave/slaves
* rsync the binary across using rsync
control:~/cbuild/build/gcc-4.8~svn185503/gcc-*cortexa9*xz .
* Extract the binary and have at it
The board will drop back into the queue after 48 hours. You can
release it early by doing a 'killall sleep'. Please do any work under
/scratch/cbuild/slave/slaves as this is automatically deleted when the
next job starts.
Zhenqiang, could you add this to the jobs page please?
-- Michael
I've create a blueprint covering the basic functions in libav that are
implemented as inline assembly:
https://blueprints.launchpad.net/gcc-linaro/+spec/investigate-libav-inline-…
These are a mix of multiplies, clipping, byte swap, and unaligned
access. We do OK on half of them but at least byte swap and 32x32 ->
top half of 64 aren't as good as they could be.
Let's discuss the investigation at the next performance meeting.
-- Michael
Hi,
Linaro bugs:
- #926472: Native gdb can't know multithreads of Android processes
Tried to reproduce but couldn't do a GDB build similar to
the bug reporter's. Found a workaround for him anyway.
- #942529: gdb failed to debug application (gdb reports about
internal error)
Reproduced the bug and found out it's fixed in GDB 7.4. It's a bug
in Ubuntu GDB not Linaro, so reassigned to the Ubuntu project.
Linaro GDB is already at version 7.4 so we're good.
- #954714: dropped patch reintroduces gcore relro backtrace problem
Reviewed the proposed patch. It's good.
GDB for Android:
- Started creating patches for build problems when trying to compile
gdbserver for Android. Will have patches to submit in the next
few days.
- Studied libthread_db.c to see what's special about it that it has
to be statically linked. Didn't find anything and indeed Android's
own libthread_db.so works fine. Didn't get an answer yet when
I asked about it on the Android mailing list.
--
[]'s
Thiago Jung Bauermann
Linaro Toolchain Working Group
==Progress===
* Did some work to improve code generation for addressing modes in VFP
registers.
* Looked at some more cases and detected that there are 2 areas of
improvement for
the future
* shrink-wrapping
* Too many unnecessary ldm / stm stacking for cases with small
structures being
passed .
* Committed configure.ac changes.
* Committed MALLOC_ABI_ALIGNMENT changes.
* Looked at some upstream testsuite failures. There are about 54 too
many test failures in vect.exp that
need to be looked at at some point.
=== Plans ===
* Push vfp wb patches upstream.
* Resurrect partial-partial PRE
Absences.
* 1 week holiday sometime before that - to be booked
* Linaro Connect Q2.12 - May 28 - June 1 - travel booked - hotel to be booked.
I've created blueprints for the libav missed optimisations and added
references to Ramana's page at:
https://wiki.linaro.org/RamanaRadhakrishnan/Sandbox/RRQ112ConnectLibavgcc46…
Those that are new and in progress I've assigned to the relevant
person. Ulrich, I couldn't find a end of loop counter blueprint so I
created a new one.
-- Michael
This is the first announcement on upcoming changes to the supported
Linaro GCC versions.
GCC 4.7 is expected out in the next two weeks. We plan to switch to
4.7 for the Linaro GCC 2012.04 release and, as part of that, will put
Linaro GCC 4.6 into maintenance and retire Linaro GCC 4.5. While in
maintenance we will continue to update, fix bugs, and do releases on
4.6. No further changes or releases will be made to 4.5. All
historical releases and branches will stay available.
For more informatio, please see the flyer at:
https://wiki.linaro.org/WorkingGroups/ToolChain/Flyer
especially the section on Lifecycle:
https://wiki.linaro.org/WorkingGroups/ToolChain/Flyer#Lifecycle
The formal change notes will be sent after the 2012.04 release.
-- Michael
Hi,
OpenEmbedded:
* rebased against current OE-core
* my patch that introduces an image fs alignment is now upstream
* noticed that the newly introduced bdwgc recipe (the Hans Boehm
Garbage collector which is needed by guile) uses a version of libatomic
that fails when building in Thumb mode
* has been fixed upstream already
* pulseaudio/libatomics-ops_1.2.bb has the same issue and just sets
ARM_INSTRUCTION_SET to "arm" (probably until a new version gets pulled in)
* we can use the same workaround till then
* found a bug in the recipe for the Linaro external binary toolchain
where some header files are placed into a wrong directory during the
install step
* which prevents python from being built
* now fixed
Please note that I'll be on vacation till 04/13/2012.
Regards,
Ken
Hi Ken. I've made a meta-linaro project on Launchpad and created the
near term blueprints. See:
https://blueprints.launchpad.net/meta-linaro
You're almost done with the initial layer work. Next is scripting up
the build and integrating with LAVA followed by turning on the build
for other architectures.
I've dropped the build in the cloud investigation. Let's use
tcserver01 as it works and is fast enough. Keep an eye on the
validation lab cloud the Validation guys are talking about - we might
shift there later.
I've sent the draft card to Loïc who will massage the text and get it
on the TSC agenda. The current blueprints focus on toolchain
validation and come to a hard stop past there. Once we have TSC
approval we can go further and talk with the Platforms guys about who
does what.
-- Michael
