- linaro-toolchain - lists.linaro.org

Semi-hosting on v8 Foundation Model using gnu tools

by Padgett Don-B43265

The v8 Foundation Model User Guide has a bare metal hello world example that uses semi-hosting. The Makefile uses ARM tools, however. Is there equivalent support for this example using a bare metal version of the gnu tools, such as gcc-linaro-aarch64-none-elf-4.8-2013.04-20130422_linux.tar.xz? I took a look, but didn't see a way to do this. Of course, running the Linaro linux port on the v8 Foundation Model allows one to run hello world and much more, but I'm currently only interested in a bare metal target using gnu tools. Thanks, Don

12 years, 7 months

3
3
0 0

[ACTIVITY] 13 - 17 May 2013

by Omair Javaid

== Progress == * Backed up laptop data and did new ubuntu installation which crashed for some reason. * Wrote python script with googledoc API to automate fill up of googlespread sheet. * Created and tested patch for arm assembler compatibility fixes for gdb.dwarf test suite assembly files. == Plan == * Identify arm bugs out of gdb7.6 test results and work towards fixing them. * Update JIRA enteries with test suite failures on arm to track progress. * More work on automating googledoc spreadsheet writing using python. * 2 Day off on coming Friday and Monday.

12 years, 7 months

1
0
0 0

[ACTIVITY] 13 May - 17 May 2013

by Venkataramanan Kumar

== Progress == * AARCH64 - gprof support. Completed gprof -c support for aarch64. Got reviewed internally by Matt and Will. Patch yet to be posted. Waiting for some feedback on copyright message. *Testing GCC bootstrap and regression suite. Created a large image with help of Bero. Bootstrap fails with GCC trunk libgcc_eh.a (unwind-dw2-fde-dip.o) hidden symbol __register_frame_info is referenced bu DSO ld final link Bad value. Drilling down == Plan == * Post patches in gcc and binutils for gprof work * Continue handling builtin_return_address when -fomit-frame-pointer is enabled. * Continue gcc bootstrap and regression test.

12 years, 7 months

1
0
0 0

[ACTIVITY] Week 20

by Yvan Roux

== Issues == * Cbuild down most of the week. == Progress == * 4.6 and 4.7 releases - Released after a painful week ! * LRA on ARM and AArch64: - Enabled on AArch64, but it leads to an ICE too. - Applied Brice's ARM patches didn't solved the issue. - Looked at the documentation/comments to understand the process. - Debug ongoing. == Plan == * Continue on LRA

12 years, 7 months

1
0
0 0

[ACTIVITY] Week 20

by Zhenqiang Chen

== Issues == * None == Progress == * Continue on conditional compare. - Mix fixes for bootstrap. * Update shrink-wrap patches according to comments and retest them on Pandaboard and Chromebook. * Prebuild 2013.05 Linaro toolchain locally. - gdb related local patches need rework. == Plan == * Continue on conditional compare to bootstrap. * Linaro toolchain 2013.05 binary release. Best Regards! -Zhenqiang

12 years, 7 months

1
0
0 0

[ACTIVITY] 13-17 May 2013

by Kugan

== Progress == http://cards.linaro.org/browse/TCWG-13 - Resolved http://cards.linaro.org/browse/TCWG-14 - Modified patch Posted upstream for review == Plan == http://cards.linaro.org/browse/TCWG-14 - Address and review comments http://cards.linaro.org/browse/TCWG-55 - Reproduce it and find the reason for specfp regression

12 years, 7 months

1
0
0 0

[ANNOUNCE] Linaro GDB 7.6 2013.05 released

by Matthew Gretton-Dann

The Linaro Toolchain Working Group is pleased to announce the release of Linaro GDB 7.6. Linaro GDB 7.6 2013.05 is the first release in the 7.6 series. ***NOTE*** Linaro GDB 7.6 2013.05 is identical to the FSF GDB 7.6 release, except for the change in version number and Linaro branding, since all Linaro GDB features were already accepted upstream and are included in the FSF release as-is. Future releases in the Linaro GDB 7.6 series may include additional ARM-focused bug fixes and enhancements. The source tarball is available at: https://launchpad.net/gdb-linaro/+milestone/7.6-2013.05 More information on Linaro GDB is available at: https://launchpad.net/gdb-linaro -- Matthew Gretton-Dann Linaro Toolchain Working Group matthew.gretton-dann(a)linaro.org

12 years, 7 months

1
0
0 0

[ANNOUNCE] Linaro GCC 4.8, 4.7 and 4.6 2013.05 released

by Yvan Roux

The Linaro Toolchain Working Group is pleased to announce the 2013.05 release of Linaro GCC 4.8, Linaro GCC 4.7 and Linaro GCC 4.6. Linaro GCC 4.8 2013.05 is the second release in the 4.8 series. Based off the latest GCC 4.8.0+svn198615 release, it includes performance improvements and bug fixes. Interesting changes include: * Updates to GCC 4.8.0+svn198615 * Backport of support for prologue/epilogues using LDRD and STRD in ARM mode * Backport of support for further AArch64 instructions * Backport of support for further ARMv8 AArch32 instructions. Linaro GCC 4.7 2013.05 is the fourteenth release in the 4.7. Based off the latest GCC 4.7.3+svn198701 release, this is the first release after entering maintenance. Interesting changes include: * Updates to GCC 4.7.3+svn198701 * Includes arm/aarch64-4.7-branch up to svn revision 198689 Linaro GCC 4.6 2013.05 is the 27th release in the 4.6 series. Based off the latest GCC 4.6.4+svn197894 release, this is the fourteenth release after entering maintenance and the final one. Interesting changes include: * Updates to 4.6.4+svn197894 The source tarball is available from: https://launchpad.net/gcc-linaro/+milestone/4.8-2013.05 https://launchpad.net/gcc-linaro/+milestone/4.7-2013.05 https://launchpad.net/gcc-linaro/+milestone/4.6-2013.05 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.8/4.8-2013.05 https://launchpad.net/gcc-linaro/4.7/4.7-2013.05 https://launchpad.net/gcc-linaro/4.6/4.6-2013.05 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

12 years, 7 months

1
0
0 0

[ACTIVITY] Week 20

by Renato Golin

== Progress == * 3.3 Release - Bootstrapping, testing, fixing bugs, etc. - RC1 released on Tuesday http://people.linaro.org/~rengolin/llvm/ - Fix for C11 atomics on Linux http://llvm.org/bugs/show_bug.cgi?id=15429 - Fix for zero extend vector bug in test-suite http://llvm.org/bugs/show_bug.cgi?id=15970 * Test-Suite - ClamAV fails on Calxeda, same as PPC64 (bad test) * Self-Host Buildbot - Re-purposing the Panda back to buildbot service - Buildbot passing green, setting it up on Build Master == Issues == Calxeda gets turned off quite regularly, which messes up any long term commitment you might have for them. == Plan == * Install Ubuntu on Chromebook, run benchmarks with 3.3 RC1 * Try to revive LLVM CBuild job if it's any different than our current buildbot * Try to setup benchmark jobs for LLVM, either buildbots, CBuild, or whatever * Stay alert for RC2 and re-run release process on them

12 years, 7 months

1
0
0 0

[ACTIVITY] Week 20

by Will Newton

== Progress == * Finished porting ld-ifunc tests to AArch64. * Requested a relocation number for R_AARCH64_IRELATIVE. * Tested AArch64 ifunc code natively to run generic ifunc tests. * Investigated gdb bug #1175525 and submitted workaround patch to gdb-patches. * Started DeveloperTools and LibraryPerformance wiki pages. * Submitted initial version of AArch64 binutils patch with temporary reloc number. == Issues == * None. == Plan == * Complete process of getting R_AARCH64_IRELATIVE allocated. * Feedback on binutils AArch64 ifunc patch. * Feedback on slightly hacky gdb patch. * bionic memcpy. -- Will Newton Toolchain Working Group, Linaro

12 years, 7 months

1
0
0 0

[ACTIVITY] 13-17 May 2013

by Christophe Lyon

== Progress == * Disable-peeling: analyzed regression on one bench. * Libsanitizer/aarch64: - porting will require more effort than aarch32. - some syscalls are not supported by aarch64 - libsanitizer expects frame to grow downwards (true on aarch32, false on aarch64) * PGO/LTO bug reported by Doko: updating board environment to reproduce it * Internal support == Next == * Disable-peeling: see how to disable too aggressive vectorization * Revert-coalesce-vars: discuss how to handle it with the team * Neon intrinsics: continue improving crc with vuzp * Neon intrinsics tests: handle feedback if any * PGO/LTO bug: reproduce it

12 years, 7 months

1
0
0 0

[ACTIVITY] report week 20

by Peter Maydell

Progress: * VIRT-49, VIRT-50 [cp15 migration, reset] ** last bits of patch cleanup complete; realised I could test KVM migration without any timer or vgic patches; did so and sent first version of patches out to qemu-devel * VIRT-55: ** started to draft basic notes on what we want to test: https://wiki.linaro.org/PeterMaydell/MigrationTesting * misc ** reviewed Huawei's aarch64 tcg target patches; there are some issues they need to fix but overall looking good ** fixed a last-minute bug in the versatilepb PCI controller model (some changes we made earlier in the release cycle wouldn't work with newer Linux kernels) Plans: * deal with any code review feedback on patchset * set up a raring/aarch64 cross build environment (got partway through this, waiting for wookey to update some packages) * more in-depth review/test of John Rigby's mach-virt, aarch64 patchsets * VIRT-55: write up how to test migration (and talk to Andre about what he's doing testing-wise) -- PMM

12 years, 7 months

1
0
0 0

hot spot on the vsub.f32 instruction

by YongQin Liu

Hi, All The attachment file is analysed by the streamline tool. How to do you think about the vsub.f32 hot spot there? Is there any way we can improve that? -- Thanks, Yongqin Liu --------------------------------------------------------------- #mailing list linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org> http://lists.linaro.org/mailman/listinfo/linaro-android linaro-validation(a)lists.linaro.org <linaro-dev(a)lists.linaro.org> http://lists.linaro.org/pipermail/linaro-validation

12 years, 7 months

6
9
0 0

[ACTIVITY] 6 - 10 May 2013

by Omair Javaid

== Progress == * Filled up the googledoc comparison sheets of gdb 7.6 test suite run in different configuration on chromebook and x86. * Filled up the googledoc comparison sheets of gdb 7.5.1 test suite run in different configuration on chromebook and x86. * Compared GDB 7.6 and 7.5.1 results which show good improvements in gdb 7.6. == Plan == * Repair my laptop's ubuntu installation which crashed for some reason. * Submit patch to fix dwarf test suite in gdb 7.6 * Investigate gdb 7.6 gdb.base failures on arm and try to figure out causes + possible solution. * Try to figure out a way automate a comparison of two test suite results and upload them to googledocs.

12 years, 7 months

1
0
0 0

bitbake linaro-image-sdk fails on 13.04

by Aparna Mandke

Hi, I downloaded 13.04 version and tried to compile linaro-image-sdk and linaro-image-lamp. Both these builds fail with the following error. However, I could compile core-image-minimum. Can somebody help me with this issue? Is there any quick workaround. Mostly, I do not need ltp package. Thanks, Aparna aarch64-oe-linux-gcc -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed --sysroot=/home/kvs/aparna/openembedded/build/tmp-eglibc/sysroots/genericarmv8 -O2 -pipe -g -feliminate-unused-debug-types -g -O2 -fno-strict-aliasing -pipe -Wall -DTST_USE_NEWER64_SYSCALL=1 -I/home/kvs/aparna/openembedded/build/tmp-eglibc/work/aarch64-oe-linux/ltp/20120903-r2/ltp-20120903/testcases/kernel/include -I/home/kvs/aparna/openembedded/build/tmp-eglibc/work/aarch64-oe-linux/ltp/20120903-r2/ltp-20120903/testcases/kernel/syscalls/getdents -I/home/kvs/aparna/openembedded/build/tmp-eglibc/work/aarch64-oe-linux/ltp/20120903-r2/ltp-20120903/testcases/kernel/syscalls/getdents/../utils -I../../../../include -I../../../../include -D_FILE_OFFSET_BITS=64 -DOFF_T=__off64_t -c -o getdents04_64.o getdents04.c | In file included from getdents01.c:57:0: | getdents.h: In function 'getdents': | getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in this function) | getdents.h:60:16: note: each undeclared identifier is reported only once for each function it appears in | In file included from getdents02.c:53:0: | getdents.h: In function 'getdents': | getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in this function) | getdents.h:60:16: note: each undeclared identifier is reported only once for each function it appears in | In file included from getdents03.c:56:0: | getdents.h: In function 'getdents': | getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in this function) | getdents.h:60:16: note: each undeclared identifier is reported only once for each function it appears in | In file included from getdents04.c:56:0: | getdents.h: In function 'getdents': | getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in this function) | getdents.h:60:16: note: each undeclared identifier is reported only once for each function it appears in | make[4]: *** [getdents01] Error 1 | make[4]: *** Waiting for unfinished jobs.... | make[4]: *** [getdents02] Error 1 | In file included from getdents03.c:56:0: | getdents.h: In function 'getdents': | getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in this function) | getdents.h:60:16: note: each undeclared identifier is reported only once for each function it appears in | make[4]: *** [getdents03] Error 1 | In file included from getdents02.c:53:0: | getdents.h: In function 'getdents': | getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in this function) | getdents.h:60:16: note: each undeclared identifier is reported only once for each function it appears in | make[4]: *** [getdents04] Error 1 | make[4]: *** [getdents03_64.o] Error 1 | In file included from getdents04.c:56:0: | getdents.h: In function 'getdents': | getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in this function) | getdents.h:60:16: note: each undeclared identifier is reported only once for each function it appears in | In file included from getdents01.c:57:0: | getdents.h: In function 'getdents': | getdents.h:60:16: error: 'SYS_getdents' undeclared (first use in this function) | getdents.h:60:16: note: each undeclared identifier is reported only once for each function it appears in | make[4]: *** [getdents02_64.o] Error 1 | make[4]: *** [getdents04_64.o] Error 1 | make[4]: *** [getdents01_64.o] Error 1 | make[4]: Leaving directory `/home/kvs/aparna/openembedded/build/tmp-eglibc/work/aarch64-oe-linux/ltp/20120903-r2/ltp-20120903/testcases/kernel/syscalls/getdents' | make[3]: *** [all] Error 2 | make[3]: Leaving directory `/home/kvs/aparna/openembedded/build/tmp-eglibc/work/aarch64-oe-linux/ltp/20120903-r2/ltp-20120903/testcases/kernel/syscalls' | make[2]: *** [all] Error 2 | make[2]: Leaving directory `/home/kvs/aparna/openembedded/build/tmp-eglibc/work/aarch64-oe-linux/ltp/20120903-r2/ltp-20120903/testcases/kernel' | make[1]: *** [all] Error 2 | make[1]: Leaving directory `/home/kvs/aparna/openembedded/build/tmp-eglibc/work/aarch64-oe-linux/ltp/20120903-r2/ltp-20120903/testcases' | make: *** [testcases-all] Error 2 | ERROR: oe_runmake failed | ERROR: Function failed: do_compile (see /home/kvs/aparna/openembedded/build/tmp-eglibc/work/aarch64-oe-linux/ltp/20120903-r2/temp/log.do_compile.6470 for further information) ERROR: Task 349 (/home/kvs/aparna/openembedded/openembedded-core/meta/recipes-extended/ltp/ ltp_20120903.bb, do_compile) failed with exit code '1'

12 years, 7 months

2
1
0 0

[ACTIVITY] 6 - 10 May 2013

by Kugan

== Done == http://cards.linaro.org/browse/TCWG-14 - Posted patch upstream for review http://cards.linaro.org/browse/TCWG-55 - benchmarking ongoing with git bisect http://cards.linaro.org/browse/TCWG-14 - Discussed the results with ARM maintainers and pinged the original patch. == Plan == http://cards.linaro.org/browse/TCWG-55 - Find the reason for spec2k fp performance regression. http://cards.linaro.org/browse/TCWG-14 - plan action based on review.

12 years, 7 months

1
0
0 0

[ACTIVITY] 6 May - 12 May 2013

by Venkataramanan Kumar

== Progress == * AARCH64 - gprof support. Submitted GCC patches to generate profile call. Also applied the review comments from Marcus and tested patches for aarch64-none-elf. http://gcc.gnu.org/ml/gcc-patches/2013-05/msg00597.html * Setup a Ubuntu machine at Office. Ran GCC testsuite with on openembeded/V8 model ref: http://people.linaro.org/~hrw/oe/vekumar/. This image has updated gcc and glibc and enables gprof. During bootstrap GCC build failed due to space getting over. Need to create a larger image. * Looking at how to handle builtin_return_address when -fomit-frame-pointer is enabled. GCC saves frame pointer for the function alone where builtin_return_address is used. Callers of the function may not have set up the frame yet. == Plan == * Continue gprof "-c" option support in binutils * Continue handling builtin_return_address when -fomit-frame-pointer is enabled. * Continue gcc bootstrap and regression suite after creating a larger image.

12 years, 7 months

1
0
0 0

[ACTIVITY] Week 19

by Zhenqiang Chen

== Issues == * None == Progress == * Investigate u-boot crash issue (lp:1178530). - Root cause: unaligned access. - "-mno-unaligned-access" can disable unaligned access (README will be updated from 2013.05 release). - Linaro release supports armv4t multilib option for u-boot build: -marm -march=armv4t -mfloat-abi=soft * Conditional compare. - Investigate vrp pass to simplify conditional compare. - Investigate reassoc pass to handle conditional compare - All experimental codes are pushed to lp:~zhenqiang-chen/gcc-linaro/4.8-conditional-compare * Fix binary release tarball name issue (lp:1174350) and update release document. == Plan == * Continue on conditional compare. Best Regards! -Zhenqiang

12 years, 7 months

1
0
0 0

[ACTIVITY] Week 18

by Renato Golin

== Progress == * 3.3 Release - Running tests on Pandas and Calxeda, Ubuntu 12.04 and 12.10 - Chromebook arriving next week - Calxedas died a couple of times this week for no reason (somebody else turned it off?) - Many bootstrap failures on 12.04: check-all, test-suite, etc on all phases - Fixing a bug that allows to bootstrap on Ubuntu 12.10 * EuroLLVM 2013 - Published the questionnaire results, wrote a post on the blog - http://blog.llvm.org/2013/05/eurollvm-2013-paris-france.html * Extra - Studying C++11 atomics == Issues == There's no way to tell when someone will turn the Calxeda server off, so relying on its results or usability is folly. Not to mention that the designers should have had a bit more care on the interface to power up and configure nodes. == Plan == * Spend the weekend testing on the Pandaboard with Ubuntu 12.10 and see if the fix is good, commit * Install Ubuntu on Chromebook arriving on Monday, run release tests on them * Hope that Ubuntu 12.10 will be less hemorragic than 12.04 for the LLVM release...

12 years, 7 months

1
0
0 0

[ACTIVITY] 6-10 May 2013

by Christophe Lyon

Short week (3 days) == Progress == * Disable-peeling: got results vs reference, shared with team. * Revert-coalesce vars: got results vs reference, showing regressions. * Libsanitizer: committed upstream. * Neon intrinsics: shared initial proposal of dejagnu-ization of my existing tests. * Branch reviews * Internal support == Next == * Disable-peeling: investigate regression on eon * Revert-coalesce: discuss how to handle it with team * Libsanitizer: enable on aarch64 * Neon intrinsics: continue improving crc with vuzp * Neon intrinsics tests: continue dejagnu-ization

12 years, 7 months

1
0
0 0

[ACTIVITY] Week 19

by Will Newton

== Progress == * Four day week and traditional bank holiday cold slowed progress. * Tested glibc memcpy patch on big endian and got it committed. * Submitted some generic IFUNC patches for binutils upstream. * Further work on AArch64 IFUNC support in binutils. == Issues == * cbuild seems to not be doing much building at the moment. == Plan == * Complete AArch64 IFUNC support and submit a patch. * Look further at gdb bug if I get time. -- Will Newton Toolchain Working Group, Linaro

12 years, 7 months

1
0
0 0

[ACTIVITY] report week 19

by Peter Maydell

[three day week] Progress: * VIRT-49 [cp15 migration] ** lots of patch cleanup; nearly ready to submit but ideally I'd like to test KVM migration with Andre's kernel changes first ** improved arndale setup by switching to USB hard disk; confirmed I can build and boot my own kernel * VIRT-50 [cp15 reset] ** it turns out that the VIRT-49 patches on their own break reset handling for the KVM case, so we need to include VIRT-50 work in the same patchset. Fortunately it turns out to be a small extension; patch done and tested, and will be submitted as part of the VIRT-49 patchset * misc ** discussions about early-printk in a virtual machine. I still think it's important to be able to have a device tree binding to tell the kernel where its early-printk uart is. Grant Likely said he and Nico actually tossed this idea around in the past, it just never got implemented. Plans: * VIRT-49/50: test against Andre's kernel timer save/load patches, then submit * more in-depth review and test of John Rigby's mach-virt and aarch64 patchsets -- PMM

12 years, 7 months

1
0
0 0

[ACTIVITY] Week 19

by Yvan Roux

== Issues == * None == Progress == * Short week (3 days) * LRA on ARM and AArch64: - Debug libgcc build failure ongoing. == Plan == * Merge review roster * Continue on LRA

12 years, 7 months

1
0
0 0

arm-linux-gnueabi- error messages.

by mind entropy

Hi, I am using arm gcc toolchain present in ubuntu 13.04. I get the following error messages when I compile linux kernel for the mini2440 board. arch/arm/kernel/entry-armv.S: Assembler messages: arch/arm/kernel/entry-armv.S:228: Error: ARM register expected -- `ldr r6,[ r5,#(0x10)]' arch/arm/kernel/entry-armv.S:228: Error: ARM register expected -- `ldr r0,[ r5,#(0x14)]' arch/arm/kernel/entry-armv.S:459: Error: ARM register expected -- `ldr r6,[ r5,#(0x10)]' arch/arm/kernel/entry-armv.S:459: Error: ARM register expected -- `ldr r0,[ r5,#(0x14)]' make[1]: *** [arch/arm/kernel/entry-armv.o] Error 1 make: *** [arch/arm/kernel] Error 2 These error messages started appearing after i upgraded to 13.04. Is there any problem with the toolchain. gcc details: arm-linux-gnueabi-gcc -v Using built-in specs. COLLECT_GCC=arm-linux-gnueabi-gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc-cross/arm-linux-gnueabi/4.7/lto-wrapper Target: arm-linux-gnueabi Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.7.3-1ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-4.7/README.Bugs --enable-languages=c,c++,go,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.7 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/arm-linux-gnueabi/include/c++/4.7.3 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libitm --enable-plugin --with-system-zlib --enable-objc-gc --with-cloog --enable-cloog-backend=ppl --disable-cloog-version-check --disable-ppl-version-check --enable-multiarch --enable-multilib --disable-sjlj-exceptions --with-arch=armv5t --with-float=soft --disable-werror --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=arm-linux-gnueabi --program-prefix=arm-linux-gnueabi- --includedir=/usr/arm-linux-gnueabi/include Thread model: posix gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) Thanks, Gautam.

12 years, 7 months

1
0
0 0

Undefined __aeabi_uidiv references in blobs with 4.8 toolchain

by Bernhard Rosenkränzer

Hi, I'm running into an interesting problem with driver blobs when building Android with the 4.8 toolchain: E/libEGL ( 1219): load_driver(/vendor/lib/egl/libEGL_POWERVR_SGX540_120.so): Cannot load library: soinfo_link_image(linker.cpp:1635): could not load library "libIMGegl.so" needed by "libEGL_POWERVR_SGX540_120.so"; caused by soinfo_link_image(linker.cpp:1635): could not load library "libsrv_um.so" needed by "libIMGegl.so"; caused by soinfo_relocate(linker.cpp:975): cannot locate symbol "__aeabi_uidiv" referenced by "libsrv_um.so"... __aeabi_uidiv is a libgcc.a function (Android doesn't have libgcc_s) - and the blob makers didn't link libgcc.a properly, so it is understandable why this would be missing. However, Android's libc has an ugly but (up until now) working workaround that is supposed to address this sort of issue. It includes libgcc_compat.c, which comes down to #define COMPAT_FUNCTIONS_LIST \ XX(__aeabi_uidiv) \ ... (same for other libgcc functions) #define XX(f) extern void f(void); COMPAT_FUNCTIONS_LIST #undef XX void __bionic_libgcc_compat_hooks(void) { #define XX(f) f(); COMPAT_FUNCTIONS_LIST #undef XX } Running nm on libc.so shows the symbol is actually in libc.so, and it seems to be visible. $ nm /system/lib/libc.so |grep aeabi_uidiv 0004f5d8 t __aeabi_uidiv 0004f680 t __aeabi_uidivmod libsrv_um.so is linked to libc too, so it should see it... $ objdump -x /vendor/lib/libsrv_um.so |grep libc.so NEEDED libc.so Can anyone think of a reason why this would work fine if the system is built with the 4.7 toolchain, but break with 4.8? My first thought was that 4.8 might have miscompiled the dynamic linker - but the problem remains if I copy in /system/bin/linker from the 4.7 build. ttyl bero

12 years, 7 months

2
9
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain