Linaro QEMU 2011.06 released
The Linaro Toolchain Working Group is pleased to announce the release of Linaro QEMU 2011.06. Linaro QEMU 2011.06 is the latest monthly release of qemu-linaro. Based off upstream (trunk) QEMU, it includes a number of ARM-focused bug fixes and enhancements. This release introduces two new features; these are still experimental so please report any issues: - A model of the Gumstix Overo board; this is an OMAP3 based system similar to Beagle but with the advantage of having supported onboard ethernet. - USB keyboard and mouse support, if your kernel includes support for the OMAP3 OHCI controller (not just EHCI). Try adding "-device usb-kbd -device usb-mouse" to your QEMU command line for Beagle or Overo models. Other interesting changes include: - A fix for the lack of graphics output on the Beagle model when running the Linaro 11.05 final release image - Suppression of the "Bad register 0x00f8" warnings provoked by the Linaro 11.05 final release kernels - As usual, various minor correctness fixes and other upstream changes Known issues: - The beagle and beaglexm models still do not support USB networking - There are some gcc 4.6 warnings about "variable set but not used" which have not yet been resolved; Ubuntu Oneiric's gcc makes these non-fatal, but if you're building with an upstream gcc 4.6 you may need to add the "--disable-werror" option to configure The source tarball is available at: https://launchpad.net/qemu-linaro/+milestone/2011.06 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 ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] Weekly status
- Opened PR49385. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49385 - Committed SMS patch to fix recent bootstrap fail on ARM with SMS flags http://gcc.gnu.org/ml/gcc-patches/2011-06/msg00960.html - Committed SMS patch to Fix calculation of row_rest_count http://gcc.gnu.org/ml/gcc-patches/2011-06/msg01008.html Continue with Spec2006 analysis https://wiki.linaro.org/Internal/ToolChain/Benchmarks - Next two weeks (17 Jun to 2 July) --- vacation. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] June 12-16
Hi, - fix vectorizer testsuite failures on ARM - committed - committed a fix of a bug in the vectorizer revealed by the widen-mult patch - committed an improvement of peeling heuristic - reduce over-widening in case of multiplication by a constant (improves vectorized rgbyiq by almost 2x) - committed - started backporting to gcc-linaro-4.6 Ira ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Chromium browser FTBFS on armel
Hi Yesterday I looked at bug [1] in chromium-browser but checked oneiric version: 12.0.742.91~r87961. It failed on linking to CUPS libraries so I looked at upstream repository and found fix [2]. With patch applied it failed on same place: LINK(target) out/Release/chrome [keep-alive] czw, 16 cze 2011, 18:21:39 CEST (441 min) /usr/bin/ld.bfd.real: out/Release/obj.target/third_party/cacheinvalidation/../../cacheinvalidation_proto_cpp/gen/protoc_out/google/cacheinvalidation/internal.pb.o(.text._ZN12invalidation21ClientToServerMessage27MergePartialFromCodedStreamEPN6google8protobuf2io16CodedInputStreamE+0x7d2): unresolvable R_ARM_THM_CALL relocation against symbol `operator new(unsigned int)@@GLIBCXX_3.4' /usr/bin/ld.bfd.real: final link failed: Nonrepresentable section on output collect2: ld returned 1 exit status make[1]: *** [out/Release/chrome] Error 1 make[1]: Leaving directory `/home/hrw/devel/porting-jam/chromium-browser-12.0.742.91~r87961/build-tree/src' make: *** [debian/stamp-makefile-build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 According to bugs [3][4] package may work when built without -fPIE but (as Loic wrote in [3]) "-fPIE is needed for some security features and web browsers are a critical piece of software that we want to protect". May someone take a look at this issue? One warning: this fail happens after 440 minutes of build on PandaBoard with usb hdd (took 1.8GB of space). If needed I can provide account on my panda with access to build directory (but this rather tomorrow then today) - IPv6 address only. 1. https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/791283 2. http://git.chromium.org/gitweb/?p=chromium/chromium.git;a=patch;h=c2b99f3fef6ed5d5899c281c7fc52a1983b3a361 3. https://bugs.launchpad.net/binutils-linaro/+bug/641126 4. http://code.google.com/p/chromium/issues/detail?id=55439 ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Interesting failure of vasprintf test from postler
There is a ftbfs on armel bug for postler:
https://bugs.launchpad.net/ubuntu/+source/postler/+bug/791319
Attached test compiles fine on amd64 but fails on armel:
20:16 hrw@malenstwo:postler-0.1.1$ gcc _build_/.conf_check_0/test.c
_build_/.conf_check_0/test.c: In function ‘main’:
_build_/.conf_check_0/test.c:5:1: error: incompatible type for argument
3 of ‘vasprintf’
/usr/include/stdio.h:396:12: note: expected ‘__gnuc_va_list’ but
argument is of type ‘char *’
Can someone explain me why this happens?
Ubuntu armel and armhf cross compilers, CSL 2011.03-42 have same
problem.
#define _GNU_SOURCE
#include
int main(char** argv, int argc)
{ char* a;
vasprintf(&a, "%s", ""); return 0; }___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Interesting failure of vasprintf test from postler
On czw, 2011-06-16 at 20:31 +0200, Marcin Juszkiewicz wrote: > There is a ftbfs on armel bug for postler: > https://bugs.launchpad.net/ubuntu/+source/postler/+bug/791319 > > Attached test compiles fine on amd64 but fails on armel: > > 20:16 hrw@malenstwo:postler-0.1.1$ gcc _build_/.conf_check_0/test.c > _build_/.conf_check_0/test.c: In function ‘main’: > _build_/.conf_check_0/test.c:5:1: error: incompatible type for argument > 3 of ‘vasprintf’ > /usr/include/stdio.h:396:12: note: expected ‘__gnuc_va_list’ but > argument is of type ‘char *’ > > Can someone explain me why this happens? > > Ubuntu armel and armhf cross compilers, CSL 2011.03-42 have same > problem. Compiled fine with gcc 4.3 from Poky toolchain. Same with Emdebian gcc-4.3 cross compiler. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Interesting failure of vasprintf test from postler
On 16 June 2011 19:37, Marcin Juszkiewicz wrote: > On czw, 2011-06-16 at 20:31 +0200, Marcin Juszkiewicz wrote: >> There is a ftbfs on armel bug for postler: >> https://bugs.launchpad.net/ubuntu/+source/postler/+bug/791319 >> >> Attached test compiles fine on amd64 but fails on armel: >> >> 20:16 hrw@malenstwo:postler-0.1.1$ gcc _build_/.conf_check_0/test.c >> _build_/.conf_check_0/test.c: In function ‘main’: >> _build_/.conf_check_0/test.c:5:1: error: incompatible type for argument >> 3 of ‘vasprintf’ >> /usr/include/stdio.h:396:12: note: expected ‘__gnuc_va_list’ but >> argument is of type ‘char *’ >> >> Can someone explain me why this happens? >> >> Ubuntu armel and armhf cross compilers, CSL 2011.03-42 have same >> problem. > > Compiled fine with gcc 4.3 from Poky toolchain. Same with Emdebian > gcc-4.3 cross compiler. Looks more to me like the old compilers are the ones with the problems and the new one is correctly throwing an error - it's supposed to have a va_list there - why would it take a string? Dave ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Interesting failure of vasprintf test from postler
On czw, 2011-06-16 at 19:48 +0100, David Gilbert wrote: > >> Ubuntu armel and armhf cross compilers, CSL 2011.03-42 have same > >> problem. > > > > Compiled fine with gcc 4.3 from Poky toolchain. Same with Emdebian > > gcc-4.3 cross compiler. > > Looks more to me like the old compilers are the ones with the problems > and the new one is correctly throwing an error - it's supposed to have > a > va_list there - why would it take a string? OK, but why it compiles fine on amd64/i386/powerpc? ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Interesting failure of vasprintf test from postler
On Fri, Jun 17, 2011 at 7:11 AM, Marcin Juszkiewicz wrote: > On czw, 2011-06-16 at 19:48 +0100, David Gilbert wrote: >> >> Ubuntu armel and armhf cross compilers, CSL 2011.03-42 have same >> >> problem. >> > >> > Compiled fine with gcc 4.3 from Poky toolchain. Same with Emdebian >> > gcc-4.3 cross compiler. >> >> Looks more to me like the old compilers are the ones with the problems >> and the new one is correctly throwing an error - it's supposed to have >> a >> va_list there - why would it take a string? > > OK, but why it compiles fine on amd64/i386/powerpc? (begin randon statement without investigation) On many architectures such as i386 va_list is a void * but on some it's a struct. Perhaps ARM uses a struct? -- Michael ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: No usb on omap3: 4.6 toolchain issue?
On Thu, Jun 16, 2011 at 3:04 AM, Paolo Pisati wrote: > On 06/08/2011 12:29 AM, Michael Hope wrote: >> >> Hi Paolo. Could you please treat this as an application problem and >> try to track it down further? It would be great if you could track it >> down to an individual function or chunk of mis-compiled code and >> supply the preprocessed source that goes with it, then we can jump >> right onto it. >> >> Does the same fault occur with a FSF 4.6.0 toolchain? > > I didn't know where to find a vanilla FSF 4.6 toolchain for arm, so i > rolled my own 4.6 toolchain using the Debian 4.6 source packages inside > a sid chroot and i can confirm the problem is there too. > > Meanwhile while googling around i found i was not the only one > experiencing this issue: > > https://lists.yoctoproject.org/pipermail/poky/2011-April/005703.html > > and > > https://lists.yoctoproject.org/pipermail/poky/2011-May/005763.html > > then the thread continued in June with some disassembly/low level > debugging and a couple of workarounds (neither of them worked for me > anyway): > > https://lists.yoctoproject.org/pipermail/poky/2011-June/006634.html > > Last but not least, i can confim this issue is present in linaro, ubuntu > and vanilla kernels going back to at least .35.x (actually the only .35 > i tested was ubuntu maverick), and it affects omap4 too. > > I couldn't test 3.0 since it kernel panics at boot (but that should be > another issue). Hi Paolo. I've had a look into this and updated the ticket. The problem is due to a change in behaviour between 4.5 and 4.6 when accessing strcuts marked with __attribute__((packed)). 4.5 would do a word-wise access where 4.6 assumes the worst and does a byte-by-byte access. There was a discussion on the GCC list: http://gcc.gnu.org/ml/gcc/2011-02/msg00035.html which petered out unfortunately. IMO the compiler is working correctly and the problem should be fixed in the kernel initially and then a long term plan worked out between the kernel and compiler. Arnd, do you want to pick up that thread? Both Ubuntu and Debian are now 4.6 based so this problem will come up more often. I think Patrik said there's a fix for this specific problem pending. -- Michael ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Chromium browser FTBFS on armel
On Fri, Jun 17, 2011 at 4:57 AM, Marcin Juszkiewicz wrote: > Hi > > Yesterday I looked at bug [1] in chromium-browser but checked oneiric > version: 12.0.742.91~r87961. It failed on linking to CUPS libraries so I > looked at upstream repository and found fix [2]. With patch applied it > failed on same place: > > LINK(target) out/Release/chrome > [keep-alive] czw, 16 cze 2011, 18:21:39 CEST (441 min) > /usr/bin/ld.bfd.real: > out/Release/obj.target/third_party/cacheinvalidation/../../cacheinvalidation_proto_cpp/gen/protoc_out/google/cacheinvalidation/internal.pb.o(.text._ZN12invalidation21ClientToServerMessage27MergePartialFromCodedStreamEPN6google8protobuf2io16CodedInputStreamE+0x7d2): > unresolvable R_ARM_THM_CALL relocation against symbol `operator new(unsigned > int)@@GLIBCXX_3.4' > /usr/bin/ld.bfd.real: final link failed: Nonrepresentable section on > output > collect2: ld returned 1 exit status > make[1]: *** [out/Release/chrome] Error 1 > make[1]: Leaving directory > `/home/hrw/devel/porting-jam/chromium-browser-12.0.742.91~r87961/build-tree/src' > make: *** [debian/stamp-makefile-build] Error 2 > dpkg-buildpackage: error: debian/rules build gave error exit status 2 > > According to bugs [3][4] package may work when built without -fPIE but > (as Loic wrote in [3]) "-fPIE is needed for some security features and > web browsers are a critical piece of software that we want to protect". > > May someone take a look at this issue? Can do. Has it been reported in upstream binutils? -- Michael ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
