The Linaro Toolchain Working Group is pleased to announce the
release of Linaro QEMU 2012.01.
Linaro QEMU 2012.01 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:
- Several bug fixes which reinstate support for running on ARM hosts
- Support for previously missing *xattr syscalls in usermode emulation
- A (dummy) model of the L2x0/PL310 L2 cache contrnoller (thanks to
Rob Herring and Mark Langsdorf of Calxeda)
Known issues:
- Graphics do not work for OMAP3 based models (beagle, overo)
with 11.10 Linaro images.
The source tarball is available at:
https://launchpad.net/qemu-linaro/+milestone/2012.01
More information on Linaro QEMU is available at:
https://launchpad.net/qemu-linaro
Hi Åsa. Well, the first proposals have arrived. I've cc'ed this to
linaro-toolchain so we have a record.
First, visit:
http://ex.seabright.co.nz/helpers/proposals
and see there are new merge requests from Ulrich with new results.
Next, login:
http://ex.seabright.co.nz/helpers/login
Your login is your Launchpad OpenID login "https://launchpad.net/~asa-sandahl"
After logging in, go back to the proposals page.
See that the fwprop-subreg merge request has a i686 and x86_64 result.
The i686 one is fine so click 'Record' and follow your nose. The
x86_64 is interesting - the fault might be real. Click 'Record'.
Note the subject line has 'regressed' in it. Ulrich will have to
investigate.
The lp-879725 results look fine so record both of those. Scanning
down the page shows that everything else is recorded so you're done!
The tool is a bit slow so don't be surprised if an operation takes ~10
s. The tool is backed by a cache so you won't see the results for ~2
hours.
-- Michael
Hi Michael,
I can't remember if I told you before, but I shall be away at the
CodeSourcery (Ok, Mentor Graphics's ESD TOOLS) annual meeting most of
next week.
I ought to be back at work on Friday. In the meantime I shall be reading
email, but not spending much time on Linaro work.
I can probably still get the GCC release process done, but if you'd
prefer Ramana did it this month then that's fine with me.
Andrew
Hi there. Linaro is about what's next and, as part of this, we should
backport any reasonable Cortex-A15 changes to our 4.6 branch.
Richard and Matthew, could you let us know directly when new patches
from ARM land upstream?
We're already doing this but I thought I'd say it out loud.
-- Michael
Hello,
I'm trying to build the Linaro GCC from source on an x86_64 Fedora 16 box.
I'm using as a guide a wiki entry I found in linaro.org site [1] that
explains how to build a native version of the compiler. But instead of a
native version I want to be able to cross-compile ARM binaries for my
target machine.
This is what I tried:
[javier@munra src]$ wget -c
http://launchpadlibrarian.net/86993387/gcc-linaro-4.6-2011.12.tar.bz2
[javier@munra src]$ tar xaf gcc-linaro-4.6-2011.12.tar.bz2
[javier@munra src]$ mkdir build && cd build
[javier@munra build]$ ../gcc-linaro-4.6-2011.12/configure
--target=arm-linux --disable-bootstrap --enable-languages=c
--prefix=/home/javier/tools
[javier@munra build]$ make -j4 && make install
But got this error:
make[2]: Leaving directory `/home/javier/src/build/gcc'
Checking multilib configuration for libgcc...
mkdir -p -- arm-linux/libgcc
Configuring in arm-linux/libgcc
configure: creating cache ./config.cache
checking for --enable-version-specific-runtime-libs... no
checking for a BSD-compatible install... /usr/bin/install -c
checking for gawk... gawk
checking build system type... x86_64-unknown-linux-gnu
checking host system type... arm-unknown-linux-gnu
checking for arm-linux-ar... arm-linux-ar
checking for arm-linux-lipo... arm-linux-lipo
checking for arm-linux-nm... /home/javier/src/build/./gcc/nm
checking for arm-linux-ranlib... arm-linux-ranlib
checking for arm-linux-strip... arm-linux-strip
checking whether ln -s works... yes
checking for arm-linux-gcc... /home/javier/src/build/./gcc/xgcc
-B/home/javier/src/build/./gcc/ -B/home/javier/tools/arm-linux/bin/
-B/home/javier/tools/arm-linux/lib/ -isystem
/home/javier/tools/arm-linux/include -isystem
/home/javier/tools/arm-linux/sys-include
checking for suffix of object files... configure: error: in
`/home/javier/src/build/arm-linux/libgcc':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
make[1]: *** [configure-target-libgcc] Error 1
make[1]: Leaving directory `/home/javier/src/build'
make: *** [all] Error 2
Before trying to compile I've installed the libgmp, libmpfr and arm cross
tool-chain [2] Fedora packages so I guess all gcc dependencies are met
(binutils, glibc, etc).
Could someone be so kind to point me out what am I doing wrong? I'm sending
as an attachment the config.log generated file.
Please let me know if you need any more information about my setup and
environment.
[1]: https://wiki.linaro.org/WorkingGroups/ToolChain/Using/GCCNative
[2]: http://fedoraproject.org/wiki/Architectures/ARM/CrossToolchain
Thanks a lot and best regards,
Javier
I've taken a stab at the medium term requirements for KVM on ARM:
https://wiki.linaro.org/WorkingGroups/ToolChain/Specs/KVMEpic
I haven't looked outside Linaro so apologies if this overlaps with
other people's plans.
Peter, this is high level and hopefully matches what's in your head.
I want to use this to do a project plan, see if it can be done in 6-9
calendar months, and see if we need more people. Are there any
implementation details that we should call out, similar to calling out
virtio and UEFI?
Rusty, this should tell you more about where we're going.
Mounir, you, Peter, and I should turn this into a basic project plan.
-- Michael
Hi,
Does anyone have anything they'd like to bring up in tomorrow's
performance call. ? I don't have any topics other than following on
action items from last time's call - which was comparing movw/ movt
with constant pools .
https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2012-01-10
Please add to it as you deem fit.
cheers
Ramana
* Linaro
Continued work on getting GCC to build on LAVA. I've ironed out a few
more bugs from my test scripts, but it's slow going because a test runs
takes a long time to run, and there are very few useful error messages
when something goes wrong.
Wrote, posted, and committed a patch to fix the "120" testsuite bug I
encountered last month. Basically the GCC testsuite's "headmerge-1"
testcase would have failed from now until September because a sloppy
regex happening to match "120" in the toolchain version string's
snapshot date. I've also backported it to upstream 4.6 and posted a
merge request for Linaro 4.6.
Continued running benchmarks for the generic tuning project.
Continued looking at optimizing 64-bit shifts. No real progress this
week though.
* Other
Monday: Public holiday.
Tuesday: Vacation.
Caught up on a mountain of email.