linaro-toolchain

linaro-toolchain@lists.linaro.org

5701 discussions

by Yvan Roux

== Progress == o Extended validation (5/10) * Dejagnu remote layout patch finalized and committed upstream (will be part of the coming 1.6 Dejagnu release) * GCC guality test fix committed in trunk. * Native armv8l validation unblocked, but still slow (more than 8hrs) Analysis on-going. * Start to work on enhancement: include cross validation and benchmark trigger. o Misc (5/10) * Lot of meetings (Internal, training, Benchmarking, ...) == Plan == o Monthly snaphsot (review backports, branch merge) o Continue on extended validation o GCC ARMv8.1 builtins fix.

10 years

[ACTIVITY] 4 - 8 April 2016

by Prathamesh Kulkarni

== This Week == * LTO (6/10) a) tcwg-128: branch out of range error - Addressing upstream reviews - Patch needs approval from Honza b) section-anchors - Understanding balanced partitioning algorithm - Working on 2nd prototype: http://people.linaro.org/~prathamesh.kulkarni/section-anchors-1.diff - Looking at regressions caused due to patch: http://people.linaro.org/~prathamesh.kulkarni/section-anchors-1-compare-res… c) submitted patch to slightly refactor lto_balanced_map: - https://gcc.gnu.org/ml/gcc-patches/2016-04/msg00341.html d) tcwg-534: ipa-comdats - found why ICE happens e) ipa-vrp - Discussions with Kugan * Validation (1/10) - Passing -static-libstdc++ works to build chromium without using chromium's sysroot. - Review 11311 - Untested script to build chromium for arm, x86: http://people.linaro.org/~prathamesh.kulkarni/build-chromium.sh * Public Holiday (2/10) * Misc (1/10) - Meetings == Next Week == - LTO: section anchors - Validation

10 years

[ACTIVITY] for week ending 8th April 2016

by Peter Smith

== Progress == Transition week into Linaro toolchain group from ARM to replace Bernie [*] - Some ARM handover work done. - Started looking into https://llvm.org/bugs/show_bug.cgi?id=24350 (TCWG-466 ADRL support) -- Checked behaviour of ADRL on armasm and GNU as -- Worked out what I need to do in LLVM to make ADRL work, looks like nothing hugely complicated but a lot of plumbing through various layers. - Started reading about AArch64 TLS descriptor implementation. I'm familiar with the AArch32 traditional model so I need to bridge the gap a bit. == Plans == - Post some review comments on Adhemeval's TLS patch with the hope of unblocking it. - Start implementing support for ADRL in the integrated assembler == Planned Absences == Holiday 18th - 22nd April (Attending ACCU conference in Bristol). I think I've put that in the shared holiday calendar correctly. [*] Hello to everyone I didn't manage to meet at Linaro Connect. I've been working in ARM's proprietary compiler team, with much of that time spent on armlink and the other non-compiler tools.

10 years

[ACTIVITY]

by Renato Golin

== Progress == * Support (2/10) - Adding more tests to D18701, covering more cases - Investigating PR27250 (user error) * Buildbots (2/10) - More work around LLDB buildbots * Background (6/10) - Code review, meetings, discussions, general support, etc. - Android / AOSP discussions, meetings - Some lab planning, meetings - Helping newcomers, meetings

10 years

[ACTIVITY] 1 April -- 8 April

by Yao Qi

# Progress # * TCWG-167, ARM reverse debugging bug fixes. [4/10] Four patches are committed. All FAILs are fixed if test case is compiled with -fomit-frame-pointer. Some FAILs when -fno-omit-frame-pointer are caused by epilogue unwinder doesn't parse epilogue correctly if FP is involved. File TCWG-562 to track it. * TCWG-545, TCWG-547, patches are pending. Maintainer is busy on something else. * Triage the regression gdb.base/jit.exp. [1/10] We need a pending patch series to address this issue. Ask Pedro how to review them. * TCWG-561, handle unavailable memory during frame unwinding. [3/10] Think about it and write a prototype. * Misc, patches review and meeting, [2/10]. # Plan # * Take a look at the slow native arm-linux-gnueabihf gdb test. * TCWG-562, Tweak epilogue unwinder to handle FP. * TCWG-545, TCWG-547, ping. * TCWG-561, finish the prototype. -- Yao

10 years

Linaro toolchain: libstdc++.so: file format not recognized; treating as linker script

by Gunnar Arndt

My dear friends, I'm trying to build C++ code for Linux running on am ARM Cortex A8 (TI AM335x). For a first try, I'm using the simplest program I can think of: /* main.cpp */ int main() { return 0; } Under Linux with the 'normal' GCC, that works fine, but under Windows 7 with the Linaro toolchain, it fails with the following message: C:\firedect\dev\workspace\Test-Linux-ARM_1> "\Program Files (x86)\GNU Tools ARM Embedded\gcc-linaro-4.9-2016.02-i686-ming w32_arm-linux-gnueabi\bin\arm-linux-gnueabi-g++.exe" main.cpp c:/program files (x86)/gnu tools arm embedded/gcc-linaro-4.9-2016.02-i686-mingw32_arm-linux-gnueabi/bin/../lib/gcc/arm-linux-gnueabi/4.9.4/../../../../arm-linux-gnueabi/bin/ld.exe:c:/program files (x86)/gnu tools arm embedded/gcc-linaro-4.9-2016.02-i686-mingw32_arm-linux-gnueabi/bin/../lib/gcc/arm-linux-gnueabi/4.9.4/../../../../arm-linux-gnueabi/lib/libstdc++.so: file format not recognized; treating as linker script c:/program files (x86)/gnu tools arm embedded/gcc-linaro-4.9-2016.02-i686-mingw32_arm-linux-gnueabi/bin/../lib/gcc/arm-linux-gnueabi/4.9.4/../../../../arm-linux-gnueabi/bin/ld.exe:c:/program files (x86)/gnu tools arm embedded/gcc-linaro-4.9-2016.02-i686-mingw32_arm-linux-gnueabi/bin/../lib/gcc/arm-linux-gnueabi/4.9.4/../../../../arm-linux-gnueabi/lib/libstdc++.so:1: syntax error collect2.exe: error: ld returned 1 exit status C:\firedect\dev\workspace\Test-Linux-ARM_1> "\Program Files (x86)\GNU Tools ARM Embedded\gcc-linaro-5.3-2016.02-i686-ming w32_arm-linux-gnueabihf\bin\arm-linux-gnueabihf-g++.exe" main.cpp c:/program files (x86)/gnu tools arm embedded/gcc-linaro-5.3-2016.02-i686-mingw32_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-gnueabihf/5.3.1/../../../../arm-linux-gnueabihf/bin/ld.exe:c:/program files (x86)/gnu tools arm embedded/gcc-linaro-5.3-2016.02-i686-mingw32_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-gnueabihf/5.3.1/../../../../arm-linux-gnueabihf/lib/libstdc++.so: file format not recognized; treating as linker script c:/program files (x86)/gnu tools arm embedded/gcc-linaro-5.3-2016.02-i686-mingw32_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-gnueabihf/5.3.1/../../../../arm-linux-gnueabihf/bin/ld.exe:c:/program files (x86)/gnu tools arm embedded/gcc-linaro-5.3-2016.02-i686-mingw32_arm-linux-gnueabihf/bin/../lib/gcc/arm-linux-gnueabihf/5.3.1/../../../../arm-linux-gnueabihf/lib/libstdc++.so:1: syntax error collect2.exe: error: ld returned 1 exit status As you can see, I have tested two versions of the toolchain, which show the same behavior. Do you have any idea what's going wrong here? I'd appreciate any help you can provide! -- Kind regards, Gunnar Arndt

10 years

Another weird behavior with arm gcc 5.3

by fengwei.yin

Hi list, I hit another weird problem after use gcc 5.3 (If I use gcc 4.9, there is no any issue) with android. With arm gcc 5.3, the C++ apps crash in one class constructor call. And gdb shows some vtbl items of the class are not relocated. With arm gcc 4.9, if set breakpoint in that constructor, we could see the vtbl items of the class are relocated. And Yes. I know the android bionic loader take response to do relocation. But if it works with gcc 4.9, I suppose bionic loader work well (unless gcc 5.3 create some new situation not handled by it). I attached the vtbl dump in gdb for gcc 5.3 and 4.9 both. We could see all valid entries in vtbl are relocated in 4.9 dump. But not all entries in vtbl are relocated in 5.3 dump (the address is not started with 0xf). Suggestions/hints are welcome. Thanks a lot. Regards Yin, Fengwei

10 years

[ACTIVITY] 27 March to 1 April 2016

by kugan

== Progress == * Type promotion pass (4/10) - Tested many different architectures - Branch created - Getting ready to benchmark * LTO (2/10) - Read VRP algorithms - new - Discussing algorithm implementation * Bugs (1/10) - PR70359 * Misc (1/10) - GCC Lists - Jenkins benchmarking jobs * Public holiday (2/10) == Plan == * LTO and VRP

10 years

Re: Question regarding the arm gcc 5.3 to build android

by Jim Wilson

On Thu, Mar 31, 2016 at 5:12 AM, fengwei.yin <fengwei.yin(a)linaro.org> wrote: > Because gcc 4.9 could build this file without any issue, I apply > --save-temps > with gcc 4.9. The ii file is attached. Can't see significant differences. There is a patch in gcc-5 to make unified assembler syntax the default. Unfortunately, it changes how extended asms work, which is perhaps a bug. The message claims it doesn't affect extended asms, but it does. https://gcc.gnu.org/ml/gcc-patches/2015-11/msg01196.html The interesting bit is the change to ASM_APP_OFF. gcc-4.9 emits a .thumb after the extended asm to switch back into thumb mode just in case. gcc-5.3 instead emits .syntax unified, which doesn't change the arm/thumb mode, just the syntax supported. This is arguably a bug, but this doesn't immediately help you. It could take a little time to get gcc-5.x source fixed, and then the compiler binary releases. Or alternatively we could fix the asm to work with gcc 5. Jim

10 years, 1 month

[ACTIVITY] Week 13

by Yvan Roux

== Progress == o Extended validation (7/10) * Fixed and improved extended native validation * Discussed proposed patch in dejagnu on process killing mechanism * Testing a fix/workaround in GCC guality tests * Re-implemented and tested fix for dejagnu remote layout o Misc (3/10) * Various meetings == Plan == o Continue on extended validation o Finalize DejaGNU patches, GCC ARMv8.1 builtins fix.

10 years, 1 month

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain