linaro-toolchain

linaro-toolchain@lists.linaro.org

2 participants
5601 discussions

Building gcc-linaro 4.6 2011.10 on ubuntu 11.10 32bit for cortex-a9

by Bruno Niklaus

hi@all i try to build the linaro-gcc on a ubuntu host 11.10 32 bit for a cortex a9. but it doenst build to the end. this is the first time ever i try to build a toolchain on my own, so excuse me if its just a beginner-mistake. somebody has any idea? configured like this *./configure --target=arm-linux-gnueabi --disable-bootstrap --enable-languages=c,c++ --with-mode=thumb --with-arch=armv7-a --with-tune=cortex-a9 --with-fpu=neon --with-float=softfp --prefix=/home/user/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10* * * no errors when configuring, but it fails during building with this error: *checking for suffix of object files... configure: error: in `/home/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10_src/arm-linux-gnueabi/libgcc': * *configure: error: cannot compute suffix of object files: cannot compile* *See `config.log' for more details.* *make[1]: *** [configure-target-libgcc] Fehler 1* *make[1]: Verlasse Verzeichnis '/home/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10_src'* *make: *** [all] Fehler 2* when i check the ./arm-linux-gnueabi/libgcc/config.log the errors which return 1 are: *configure:3028: /home/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10_src/host-i686-pc-linux-gnu/gcc/xgcc -B/home/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10_src/host-i686-pc-linux-gnu/gcc/ -B/home/user/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10/arm-linux-gnueabi/bin/ -B/home/user/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10/arm-linux-gnueabi/lib/ -isystem /home/user/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10/arm-linux-gnueabi/include -isystem /home/user/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10/arm-linux-gnueabi/sys-include -V >&5* *xgcc: error: unrecognized option '-V'* *xgcc: fatal error: no input files* *compilation terminated.* *configure:3039: $? = 1* *configure:3028: /home/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10_src/host-i686-pc-linux-gnu/gcc/xgcc -B/home/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10_src/host-i686-pc-linux-gnu/gcc/ -B/home/user/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10/arm-linux-gnueabi/bin/ -B/home/user/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10/arm-linux-gnueabi/lib/ -isystem /home/user/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10/arm-linux-gnueabi/include -isystem /home/user/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10/arm-linux-gnueabi/sys-include -qversion >&5* *xgcc: error: unrecognized option '-qversion'* *xgcc: fatal error: no input files* *compilation terminated.* *configure:3039: $? = 1* *configure:3055: /home/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10_src/host-i686-pc-linux-gnu/gcc/xgcc -B/home/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10_src/host-i686-pc-linux-gnu/gcc/ -B/home/user/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10/arm-linux-gnueabi/bin/ -B/home/user/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10/arm-linux-gnueabi/lib/ -isystem /home/user/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10/arm-linux-gnueabi/include -isystem /home/user/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10/arm-linux-gnueabi/sys-include -o conftest -g -O2 conftest.c >&5* */home/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10_src/host-i686-pc-linux-gnu/gcc/as: line 87: exec: -m: invalid option* *exec: usage: exec [-cl] [-a name] [command [arguments ...]] [redirection ...]* *configure:3058: $? = 1* *configure:3246: checking for suffix of object files* *configure:3268: /home/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10_src/host-i686-pc-linux-gnu/gcc/xgcc -B/home/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10_src/host-i686-pc-linux-gnu/gcc/ -B/home/user/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10/arm-linux-gnueabi/bin/ -B/home/user/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10/arm-linux-gnueabi/lib/ -isystem /home/user/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10/arm-linux-gnueabi/include -isystem /home/user/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10/arm-linux-gnueabi/sys-include -c -g -O2 conftest.c >&5* */home/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10_src/host-i686-pc-linux-gnu/gcc/as: line 87: exec: -m: invalid option* *exec: usage: exec [-cl] [-a name] [command [arguments ...]] [redirection ...]* *configure:3272: $? = 1* *configure: failed program was:* *| /* confdefs.h */* *| #define PACKAGE_NAME "GNU C Runtime Library"* *| #define PACKAGE_TARNAME "libgcc"* *| #define PACKAGE_VERSION "1.0"* *| #define PACKAGE_STRING "GNU C Runtime Library 1.0"* *| #define PACKAGE_BUGREPORT ""* *| #define PACKAGE_URL "http://www.gnu.org/software/libgcc/"* *| /* end confdefs.h. */* *| * *| int* *| main ()* *| {* *| * *| ;* *| return 0;* *| }* *configure:3286: error: in `/home/bruno/pandaboard/linaro/gcc-linaro-4.6-2011.10_src/arm-linux-gnueabi/libgcc': * *configure:3289: error: cannot compute suffix of object files: cannot compile* *See `config.log' for more details.*

13 years, 8 months

ARM eglibc: adding ucontext?

by Peter Maydell

At the moment ARM eglibc doesn't support the functions declared in ucontext.h: getcontext(), setcontext(), swapcontext() and makecontext(). Instead you get implementations which always fail and set errno to ENOSYS. QEMU uses these functions to implement coroutines. Although there is a fallback implementation in terms of threads, there are reasons why using the fallback is suboptimal: * its performance is worse * it will be less tested, because x86_64 and i386 both implement the ucontext functions and so QEMU on those hosts will be using different code paths * I'm not aware of a good way at configure time to detect whether getcontext() et al will always fail without actually running a test binary, which won't work in a cross-compile setup. (If eglibc just didn't provide the functions at all this would be much simpler...) We're going to care about performance and reliability of QEMU on ARM hosts as we start to support KVM on Cortex-A15, so it would be good if we could add ucontext function support to eglibc as part of that effort. Opinions? Have I missed some good reason why there isn't an ARM implementation of these functions? (I'm aware that the ucontext functions have been removed from the latest version of the POSIX spec; however AFAIK there's no equivalent functionality that replaces them so I think they're still worth having implementations of for parity with other architectures.) -- PMM

13 years, 8 months

[Activity] Week ending 21st Oct 2011

by Ramana Radhakrishnan

==Progress=== * Some upstream patch review. * Spent time looking at LP 836588 which is a case where CSE removes a particular label access in one case but doesn't remove it from the list of things in the constant pool which is quite bizarre. Will probably need some help with looking into this one. * Sent out vcvt.f32 and vcvt.f64 patches . * Connect preparation - laptop cleanup and getting it finally onto an x86_64 distribution. * Looked at some of the vec_perm / vec_rev cases in Neon with Ira. * Spent some time looking at some of Andrew's issues with generic-v7a tuning especially the cases where it was doing better and gave some suggestions. === Plans === * Prepare for Connect. * Prepare by looking at some of the large differences between various comparative benchmarks. * Some research into PGO related stuff. * Try to upstream some more of my patches in the backlog before the end of the week. * Finish off some internal paperwork. * I'm off on 26th - Wednesday. Absences. * 26th Oct - Day off. * 31st Oct - 4th Nov - Linaro Connect Q4.11 * 08 Nov - 11 Nov - Tentatively booked * Dec 19 - 31st Dec - Tentatively booked

13 years, 8 months

[ACTIVITY] 17th - 21st October

by Andrew Stubbs

Continued looking at my constant reuse optimization. I've identified a couple of hundred optimization opportunities in the whole of gcc itself, which is fewer than I had hoped. There are almost no opportunities when compiling for size as constants are always loaded from a constant pool in that case (I'm not sure why that's the case, given that this isn't any more space efficient than movw+movt, unless it can share the constant in more than one place). Backported my -mtune=native patch to Linaro GCC. Backported my generic tuning patch to Linaro GCC. Backported my pr50717 patch to Linaro, and pushed to Launchpad for testing. Analysed my benchmark results I made to aid generic tuning. Disappointingly the A8/A9 tuning is not as beneficial as one would like. In fact, the existing generic tuning patch (which was supposed to be a framework only) is actually quite competitive and gives better performance in some cases. Set more benchmarks running, this time with NEON enabled. That's about 36 hour's worth on A9, and more like 90 hours on my A8 (obviously, there's some difference in the clock speeds there). Discovered that my native tuning code won't compile with a C++ compiler (GCC Bugzilla PR50809). Tested and committed a fix upstream.

13 years, 8 months

[ACTIVITY] weekly status

by Revital Eres

Hello, Continue the implementation of estimating register pressure in SMS. Discussed with Richard some issue raised while implementing. Revital

13 years, 8 months

[ACTIVITY] Oct 17 - Oct 21

by Ulrich Weigand

== GDB == * Worked on support for cross-platform core file generation. Posted initial set of patches for comments. * Created "Toolchain support for kernel debugging" blueprint. 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, 8 months

[ACTIVITY] weekly status

by Ken Werner

Hi, I made some progress on transforming the hacks I did to get libunwind working on Android into proper patches that can go upstream. Things learned: * bionic employs OpenBSD header files that therefore lack some GNU and ARM specific defines (only small fix needed - plan is to change libunwind to work with non-patched bionic too) * Android basically provides all the functionality that is required for libunwind-ptrace - but... * no one seems to build libunwind with remote unwind functionality (including libunwind-ptrace) only * most of the issues can be avoided by changing libunwind to be more portable Regards Ken

13 years, 8 months

[ACTIVITY] w42

by Asa Sandahl

* Still having trouble with using multistrap/pdebuild-cross for cross-compiling Firefox - it looks like only x86 packages get downloaded, not armel. I have asked Wookey for advice, and he will try to reproduce the build. * Falling back to native compiling until the cross-compiling set up has been sorted out. I will now take a look at how to pass different compiler options to the Mozilla build system and how to build different parts of the program. Best Regards Åsa

13 years, 8 months

[ACTIVITY] report week 42

by Peter Maydell

(short week: 4 days) RAG: Red: Amber: Green: blog started :-) http://translatedcode.wordpress.com/ Current Milestones: || || Planned || Estimate || Actual || ||a15-usermode-support || 2011-11-10 || 2011-11-10 || || ||upstream-omap3-cleanup || 2011-11-10 || 2011-11-10 || || Historical Milestones: ||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 || ||add-omap3-networking || 2011-10-13 || 2011-10-13 || 2011-10-13 || ||a15-systemmode-planning || 2011-10-13 || 2011-10-13 || 2011-09-22 || == other == * upstream patch review, putting together pull requests * more time spent on qemu on ARM host apparent memory corruption bug (no luck yet :-(); found a Valgrind bug in the process, though (KDE:284472). This ate up way too much of this week. * A15 KVM planning work * meetings etc * moved over to patches.linaro for QEMU patch tracking -- PMM

13 years, 8 months

[ACTIVITY] October 16-19

by Ira Rosen

Hi, * widening shifts - finally committed upstream * SLP loads with different offsets and operand swaps - committed upstream * SLP with multiple types - merged to gcc-linaro-4.6 * vectorizer stuff: patch review, test fixes, discussions, bug fix * Ramana and I discussed what can be done with VEC_PERM_EXPR for NEON, and created https://blueprints.launchpad.net/gcc-linaro/+spec/support-vec-perm for this issue. Ira

13 years, 8 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain