- linaro-toolchain - lists.linaro.org

[ACTIVITY] 29 APR - 3 May 2013

by Kugan

http://cards.linaro.org/browse/TCWG-14 - Fixed 254.gap infinite loop. - Got spec2k results locally. - LSHIFT and RSHIFT introduces a performance regression for some benchmarks due to missing md pattern. Disabling it improve performance. http://cards.linaro.org/browse/TCWG-55 - Looked at the commits for specfp performance regression == Plan == http://cards.linaro.org/browse/TCWG-14 - Add the missing patterns to md to improve performance - Submit the patch upstream http://cards.linaro.org/browse/TCWG-55 - Find the reason for spec2k fp performance regression.

12 years, 2 months

1
0
0 0

[ACTIVITY] 29 APR - 3 May 2013

by Venkataramanan Kumar

== Progress == * AARCH64 - gprof support. Make GCC generate profile information (Completed). Defined macros in GCC to enable frame return address and insert profile call. Changed glibc to use generic gprof calls. Now gmon.out is generated when run in openembedded on V8 model. Used PROFILE_HOOK and generated mcount call using emit_library_call. Misc ------- 1 May was a holiday. == Plan == * Continue AARCH64 gprof support * Post patches in GCC for profile and RETURN_ADDR_RTX * Look at gprof "-c" option support in binutils * Run gcc testsuite with changes on openembeded/V8 model.

12 years, 2 months

1
0
0 0

[ACTIVITY] Week 18

by Zhenqiang Chen

== Issues == * None == Progress == * 3 day off holiday. * Investigate uninit1 pass to handle conditional compare. * Investigate lp:1173300 and lp:1174350. == Plan == * Continue on conditional compare. Best Regards! -Zhenqiang

12 years, 2 months

1
0
0 0

cortex a53/a57 support

by Kalai Narayanan-SSI

Hi, I tried compiling a hello-world program for cortex -a53/57 but, gcc does not recognize the mcpu option. Here is my command ... aarch64-linux-gnu-gcc hello_world.c -mcpu=cortex-a53 -o hello_world Does the compiler support these options? I see that lib/gcc/aarch64-linux-gnu/4.8.1/plugin/include/config/aarch64/aarch64-cores.def do have the entries for cortex a53 & a57. Thanks, Kalai

12 years, 2 months

1
0
0 0

[ACTIVITY] Week 18

by Will Newton

== Progress == * Committed binutils testsuite fix for precise, should be green in cbuild now. * Comitted binutils fix for ARM IFUNC issue. * Various small binutils fixes for AArch64. * Lots of rework of glibc memcpy patch, now up to v6. * Integrated latest bionic string functions into cortex-strings. * AArch64 IFUNC code and tests beginning to take shape. == Issues == * None. == Plan == * Another respin of glibc memcpy patch (last one?). * More work on AArch64 IFUNC. * May get time to look into gdb bug Peter found. * 4 day week due to bank holiday. -- Will Newton Toolchain Working Group, Linaro

12 years, 2 months

1
0
0 0

[ACTIVITY] report week 18

by Peter Maydell

Progress: * office move * checking up on status of licensing issues with QEMU's softfloat * cleaned up obsolete qemu blueprints in launchpad [Matt G-D is going to finish the last bits of transferring the backlog to JIRA where appropriate] * booked travel/hotel for Connect Dublin * reviewed John Rigby's mach-virt and aarch64 patches * VIRT-49 ** can run KVM with this code now, need to test migration proper (requires kernel to support arch timer state save/load), and clean up some TODOs and other cruft ** GDB is behaving oddly connected to QEMU's stub, which I think is a GDB bug (LP:1175525) but may also be a QEMU side issue Plans: * VIRT-49 debug & patch cleanup * NB: UK bank holiday next week, will be 3 day week for me -- PMM

12 years, 2 months

1
0
0 0

[ACTIVITY] Week 18

by Yvan Roux

== Issues == * None == Progress == * Short week (only 2 days) * Libunwind AArch64 support: - Did some fixes and cleanups after review. - re-submitted upstream * LRA on ARM and AArch64: - Enabled LRA on trunk for ARM target - build doesn't complete, investigation ongoing * Internal meetings == Plan == * Short week too * Continue on LRA

12 years, 2 months

1
0
0 0

[ACTIVITY]

by Renato Golin

== Progress == * EuroLLVM 2013 - Conference Mon~Tue - Analysing questionnaire's response - Writing a blog entry, reports * Shorter week, low progress == Plan == * Release - Start testing version 3.2 - Check-out frozen 3.3 and run the same tests - Make sure calxeda node is up to the task - Buy a Chromebook for further testing (?) I'll probably spend all my time worrying about the release, one way or another...

12 years, 2 months

1
0
0 0

Aarch64 toolchain build on Redhat machine

by Kalai Narayanan-SSI

Hi, I'm trying to build the aarch64 tool chain from source on a Redhat machine. I see that build.mk in the crosstool package requires a few .deb packages. If I want to build this on a Redhat machine, what are the changes I have to do? Thanks, Kalai

12 years, 2 months

2
1
0 0

ARM native version of GCC

by Sukumar Ghorai

Hi, I am looking for pre-build (binary, tar) GCC for native ARM e.g. I need to use in Angstrom FS and panda board to compile the code. Thanks & regards, Sukumar

12 years, 2 months

2
1
0 0

QT for aarch64

by Aparna Mandke

Hi, I am trying to compile Qt 4.8 for ARMv8. I need following packages. libqt4-dev libqt4-opengl-dev libphonon-dev libicu-dev libsqlite3-dev libxext-dev libxrender-dev gperf libfontconfig1-dev libphonon-dev libpng12-dev libjpeg62-dev I could not find these or any such packages on Linaro website. Is there any website which maintains packages compiled for ARMv8? I downloaded Qt4.8 source code. But it seems I need to do many hacks to get it compiled for ARMv8. Is it already available some where? Any help will be appreciated. Thanks Aparna

12 years, 2 months

3
2
0 0

[ACTIVITY] 22 - 26 April 2013

by Omair Javaid

== Progress == * Compared gdb test suite results in arm native none and arm remote gdbserver configurations. Filled up the googledoc sheet with the comparison. * Created a patch for dwarf failures still need to sync it with gdb main trunk and then need to test it on chrome book and submit after review. * Investigated gdb.mi test suite failures most of them seems to be occuring due to long delay. Will retest on chrome book and update. * Received chrome book on Friday started configuration created a recovery disk and SD card, facing a kernel panic for now. * 1:1 with Matt == Plan == * Complete chrome book configuration. * Run arm test suite in different configurations on chrome book. * Update the comparison sheet of gdb test suite results in different configurations after running tests on chrome book. * Public Holiday on 1st of May

12 years, 2 months

1
0
0 0

[ACTIVITY] 22-26 April 2013

by Venkataramanan Kumar

== Progress == * AARCH64 - Gprof support. Make GCC generate profile information (On-going). Defined hook and macros in GCC to emit "mcount" instrumented calls. Looked at ARM implementation and veener code in glibc which implements mcount. Discussed with Matt, and decided to use generic "mcount" implementation in glibc for aarch64. The generic uses built_in_return_address. Looking at defining macros and function which traverses frames back and returns the desired frame address. == Plan == * Continue gprof support work for Aarch64 Planned leaves: 1 May: Labor Day's holiday.

12 years, 2 months

1
0
0 0

[ACTIVITY] 22-26 April 2013

by Kugan

== Summary == - http://cards.linaro.org/browse/TCWG-14 - ran into space issues with chromebook and issues running spec2000 locally due to that. Finally reinstalled Ubuntu on 32GB card and set-up everything. - There is a potential issue with zero/sign extension based VRP. - 254.gap goes into infinite loop. Investigating it. - checked VRP for improvement of zero/sign extension (missing case in CRC). == Plan== - http://cards.linaro.org/browse/TCWG-14 - Find the cause for 254.gap infinite loop and fix it. - Find a solution to missing case in CRC

12 years, 2 months

1
0
0 0

[ACTIVITY] Week 17

by Zhenqiang Chen

Summary: * Enhance Linaro crosstool-ng. Details: 1. Work with Bero to release 4.8 binary build. 2. Update Linaro crosstool-ng to use ISL/CLooG for 4.8 build (lp:1172595). 3. Rebase conditional compare experimental codes to lp:gcc-linaro/4.8. Plan: * Investigate the impact of conditional compare on optimizations. Planned leaves: * 29 April - 1 May: Labor Day's holiday. Best Regards! -Zhenqiang

12 years, 2 months

1
0
0 0

[ACTIVITY] Week 17

by Yvan Roux

== Issues == * None == Progress == * Libunwind AArch64 support: - Fixed signal frame issue. - Sent patch upstream for review. - Delivered patch to OE team for early testing. * LRA on ARM and AArch64: - Start to look at what is missing. == Plan == * 3 days off next week * Continue on LRA.

12 years, 2 months

1
0
0 0

packages for aarch64 target

by Aparna Mandke

Hi, I need following packages for ARMv8 (aarch64) target. Where can I find these packages? Or do I have to download source code and compile those using linaro-cross-compiler? libqt4-dev libqt4-opengl-dev libphonon-dev libicu-dev libsqlite3-dev libxext-dev libxrender-dev gperf libfontconfig1-dev libphonon-dev libpng12-dev libjpeg62-dev Thanks Aparna

12 years, 2 months

2
1
0 0

[ACTIVITY] week 17

by Renato Golin

== Progress == * Benchmarks - Running EEMBC on a Panda - LLVM on par with GCC in code size and run time * Release Planning - Calxeda busted, delays, but got test-suite running on it - Bootstrap and test-suite fail with atomic support, investigating - Preparing a Beagleboard for conscience relief - Coordinating with other parties on hardware/testing/roles * EuroLLVM 2013 - Meetings, badges, preparations, final run * Support - Helping folks with test-suite, buildbots, reviewing patches, etc == Issues == Broke my glasses on a place impossible to fix, had to resort to epoxy while I wait for an eye test == Plan == * EuroLLVM Mon~Tue * Continue setting up release hardware/process, order some more boards * Help Sylvestre/Galina setting up Jenkins/Buildbots for release * Try to run a more substantial benchmark * Fix my glasses

12 years, 2 months

1
0
0 0

[ACTIVITY] 22-26 April 2013

by Christophe Lyon

== Progress == * Disable-peeling: had to re-spawn benchmark jobs (both reference and updated patch) * Libsanitizer: updated patch running under cbuild before updating my proposal upstream. * Neon intrinsics: - some progress on removing unnecessary moves around vuzp. - there are still some around veor * Bi-endian compiler: read article, attended call * Internal support == Next == Holidays next week == Future == * Disable peeling: analyze results * Revert-coalesce: same * Libsanitizer: sent updated patch upstream if validation OK * Neon intrinsics: continue improving crc with vuzp

12 years, 2 months

1
0
0 0

[ACTIVITY] Week 17

by Will Newton

== Progress == * Submitted binutils patch for testsuite failure on precise. * Updated glibc memcpy patch based on feedback. * Updated binutils IFUNC patch based on feedback. * Started working on AArch64 IFUNC. * Submitted a couple of cleanup patches for AArch64 binutils. == Issues == * 2 cards blocked on upstream review, 1 blocked on Android team. == Plan == * Should get binutils IFUNC patch committed Monday. * Need to ping other patches again. * More work on AArch64 IFUNC. -- Will Newton Toolchain Working Group, Linaro

12 years, 2 months

1
0
0 0

[ACTIVITY] report week 17

by Peter Maydell

Progress: * office move * VIRT-49: ** confirmed I can run KVM on the Arndale, started using it as test platform for the migration work ** I have most of the code for cp15 register migration written ** in debug phase; there is a case I hadn't considered that needs a little thought Plans: * keep pushing on with VIRT-49 * book travel/hotel for Connect Dublin * office move unpacking -- PMM

12 years, 2 months

1
0
0 0

clang + VFP

by Tom Gall

Hi. First. #include <Im-doing-something-somewhat-odd.h> I'm trying to use a current clang/llvm (current as in git checkout from just the other day) to build an opencl kernel and then link that with some code which has been compiled with gcc/g++. When the clang .o is linked to the gcc/gcc+, I'm getting /home/tgall/opencl/SNU/tmp2/cl_temp_1.tkl uses VFP register arguments, /home/tgall/opencl/SNU/tmp2/cl_temp_1.o does not the cl_temp_1.o was produced with clang. the cl_temp_1.tkl via gcc/g++. Let's dive into details. This is following in the footsteps of an open source framework called SNU which implements OpenCL. Within SNU they had a fairly old version of clang+llvm which wouldn't even build on ARM so step one has been to figure out what SNU was doing with clang and replicate this using latest clang. So given the following minimal test kernel placed into cl_temp_1.cl /* Header to make Clang compatible with OpenCL */ #define __global __attribute__((address_space(1))) int get_global_id(int index); /* Test kernel */ __kernel void test(__global float *in, __global float *out) { int index = get_global_id(0); out[index] = 3.14159f * in[index] + in[index]; } then we following the following steps: clang -mfloat-abi=hard -mfpu=neon -S -emit-llvm -x cl -I/home/tgall/opencl/SNU/src/compiler/tools/clang/lib/Headers -I/home/tgall/opencl/SNU/inc -include /home/tgall/opencl/SNU/inc/comp/cl_kernel.h /home/tgall/opencl/SNU/tmp2/cl_temp_1.cl -o /home/tgall/opencl/SNU/tmp2/cl_temp_1.ll with the resulting cl_temp_1.ll we: llc /home/tgall/opencl/SNU/tmp2/cl_temp_1.ll which results in cl_temp_1.s. Then: clang -c -mfloat-abi=hard -mfpu=neon -o /home/tgall/opencl/SNU/tmp2/cl_temp_1.o /home/tgall/opencl/SNU/tmp2/cl_temp_1.s so now in theory we should have a perflectly good cl_temp_1.o ready for linking. But first let's get the bits ready that will be built by the traditional gnu toolschain. We have: gcc -shared -fPIC -O3 -o /home/tgall/opencl/SNU/tmp2/cl_temp_1_info.so /home/tgall/opencl/SNU/tmp2/cl_temp_1_info.c and gcc -shared -fPIC -march=armv7-a -mtune=cortex-a9 -mfloat-abi=hard -mfpu=neon -fsigned-char -DDEF_INCLUDE_ARM -I. -I /home/tgall/opencl/SNU/src/runtime/hal/device/cpu -I /home/tgall/opencl/SNU/src/runtime/include -I /home/tgall/opencl/SNU/src/runtime/core -I /home/tgall/opencl/SNU/src/runtime/core/device -I /home/tgall/opencl/SNU/src/runtime/hal -I /home/tgall/opencl/SNU/src/runtime/hal/device -DTARGET_MACH_CPU -O3 -c /home/tgall/opencl/SNU/src/runtime/hal/device/cpu/hal.c -o /home/tgall/opencl/SNU/tmp2/hal.o And here we try to link it all together. g++ -shared -fPIC -march=armv7-a -mtune=cortex-a9 -mfloat-abi=hard -mfpu=neon -fsigned-char -DDEF_INCLUDE_ARM -O3 -o /home/tgall/opencl/SNU/tmp2/cl_temp_1.tkl /home/tgall/opencl/SNU/tmp2/hal.o /home/tgall/opencl/SNU/tmp2/cl_temp_1.o -L/home/tgall/opencl/SNU/lib/lnx_arm -lsnusamsung_opencl_builtin_lnx_arm -lpthread -lm and bang we're back to the error I first mentioned: /usr/bin/ld: error: /home/tgall/opencl/SNU/tmp2/cl_temp_1.tkl uses VFP register arguments, /home/tgall/opencl/SNU/tmp2/cl_temp_1.o does not so first obvious question is -mfloat-abi=hard -mfpu=neon correct for clang? tgall@miranda:~/opencl/SNU/tmp2$ clang --version clang version 3.3 Target: armv7l-unknown-linux-gnueabihf Thread model: posix Thanks for any suggestions! -- Regards, Tom "Where's the kaboom!? There was supposed to be an earth-shattering kaboom!" Marvin Martian Tech Lead, Graphics Working Group | Linaro.org │ Open source software for ARM SoCs w) tom.gall att linaro.org h) tom_gall att mac.com

12 years, 2 months

3
7
0 0

[ANNOUNCE] Linaro Toolchain Binaries 2013.04 released

by Bernhard Rosenkränzer

The Linaro Toolchain and Platform Working Groups are pleased to announce the 2013.04 release of the Linaro Toolchain Binaries, a pre-built version of Linaro GCC and Linaro GDB that runs on generic Linux or Windows and targets the glibc Linaro Evaluation Build. This will likely be the last binary release based on gcc 4.7 -- it also introduces the first gcc 4.8 based build. Uses include: * Cross compiling ARM applications from your laptop * Remote debugging * Build the Linux kernel for your board What's included: * Linaro GCC 4.7 2013.04 and Linaro GCC 4.8 2013.04 * Linaro GDB 7.5 2012.12 * A statically linked gdbserver * A system root * Manuals under share/doc/ The system root contains the basic header files and libraries to link your programs against. Interesting changes include: * gcc is updated to 4.8 (in the 4.8 builds) * rpc support in eglibc is re-enabled * Version reported by ARMv7 and AArch64 cross toolchains has been unified The Linux version is supported on Ubuntu 10.04.3 and 12.04, Debian 6.0.2, Fedora 16, openSUSE 12.1, Red Hat Enterprise Linux Workstation 5.7 and later, and should run on any Linux Standard Base 3.0 compatible distribution. Please see the README about running on x86_64 hosts. The Windows version is supported on Windows XP Pro SP3, Windows Vista Business SP2, and Windows 7 Pro SP1. The binaries and build scripts are available from: https://launchpad.net/linaro-toolchain-binaries/trunk/2013.04 Need help? Ask a question on https://ask.linaro.org/ Already on Launchpad? Submit a bug at https://bugs.launchpad.net/linaro-toolchain-binaries On IRC? See us on #linaro on Freenode. Other ways that you can contact us or get involved are listed at https://wiki.linaro.org/GettingInvolved.

12 years, 2 months

1
0
0 0

[ACTIVITY] Week 16

by Zhenqiang Chen

Summary: * ARM internal training and R/M toolchain related work. * Investigate Linaro toolchain 4.8 build issues. Details: 1. Fix several linaro toolchain 4.8 binary build issues: * nls patch need be updated to add (char *) when assigning the result of xmalloc to a char*. * gcc build pass-2 need build libbacktrace (get patch from crosstool-ng upstream). * gcc build pass-2 build with "-j4" fail. Seams build order issue. A workaround is to remove "-j4". * Mingw32 confiugre fail due to missing ISL. A workaround is to add "--without-isl" Plan: * Work with Bero to release 4.8. * Swith to ISL/CLooG for future release. Best Regards! -Zhenqiang

12 years, 2 months

1
0
0 0

Linaro GCC 4.8 - Where are prebuilt baremetal (arm-none-eabi-) toolchain binaries?

by Sugumar Natarajan

I couldn't find the arm-none-eabi- bare metal version of Linaro GCC 4.8. Please provide the link for prebuilt baremetal tool chain binaries? -Sugumar -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

12 years, 2 months

3
3
0 0

Thoughts on progressing Toolchain Working Group Lava integration

by Matthew Gretton-Dann

Paul, I've been having some thoughts about CBuild and Lava and the TCWG integration of them both. I wish to share them and open them up for general discussion. The background to this has been the flakiness of the Panda's (due to heat), the Arndale (due to board 'set-up' issues), and getting a batch of Calxeda nodes working. The following discussion refers to building and testing only, *not* benchmarking. If you look at http://cbuild.validation.linaro.org/helpers/scheduler you will see a bunch of calxeda01_* nodes have been added to CBuild. After a week of sorting them out they provide builds twice as fast as the Panda boards. However, during the setup of the boards I came to the conclusion that we set build slaves up incorrectly, and that there is a better way. The issues I encountered were: * The Calxeda's run quantal - yet we want to build on precise. * Its hard to get a machine running in hard-float to bootstrap a soft-float compiler and vice-versa. * My understanding of how the Lava integration works is that it runs the cbuild install scripts each time, and so we can't necessarily reproduce a build if the upstream packages have been changed. Having thought about this a bit I came to the conclusion that the simple solution is to use chroots (managed by schroot), and to change the architecture a bit. The old architecture is everything is put into the main file-system as one layer. The new architecture would be to split this into two: 1. Rootfs - Contains just enough to boot the system and knows how to download an appropriate chroot and start it. 2. Chroots - these contain a setup build system that can be used for particular builds. The rootfs can be machine type specific (as necessary), and for builds can be a stock linaro root filesystem. It will contain scripts to set the users needed up, and then to download an appropriate chroot and run it. The chroot will be set up for a particular type of build (soft-float vs hard-float) and will be the same for all platforms. The advantage of this is that I can then download a chroot to my ChromeBook and reproduce a build locally in the same environment to diagnose issues. The Calxeda nodes in cbuild use this type of infrastructure - the rootfs is running quantal (and I have no idea how it is configured - it is what Steve supplied me with). Each node then runs two chroots (precise armel and precise armhf) which take it in turns to ask the cbuild scheduler whether there is a job available. So my first question is does any of the above make sense? Next steps as I see it are: 1. Paul/Dave - what stage is getting the Pandaboards in the Lava farm cooled at? One advantage of the above architecture is we could use a stock Pandaboard kernel & rootfs that has thermal limiting turned on for builds, so that things don't fall over all the time. 2. Paul - how hard would it be to try and fire up a Calxeda node into Lava? We can use one of the ones assigned to me. I don't need any fancy multinode stuff that Michael Hudson-Doyle is working on - each node can be considered a separate board. I feel guilty that I put the nodes into CBuild without looking at Lava - but it was easier to do and got me going - I think correcting that is important 3. Generally - What's the state of the Arndale boards in Lava? Fathi has got GCC building reliably, although I believe he is now facing networking issues. 4. Paul - If Arndale boards are available in Lava - how much effort would it be to make them available to CBuild? One issue the above doesn't solve as far as I see it is being able to say to Lava that we can do a build on any ARMv7-A CBuild compatible board. I don't generally care whether the build happens on an Arndale, Panda, or Calxeda board - I want the result in the shortest possible time. A final note on benchmarking. I think the above scheme could work for benchmarking targets all we need to do is build a kernel/rootfs that is setup to provide a system that produces repeatable benchmarking results. Comments welcome from all. Thanks, Matt -- Matthew Gretton-Dann Toolchain Working Group, Linaro

12 years, 2 months

6
9
0 0

[ACTIVITY] 15-19 April 2013

by Christophe Lyon

== Progress == * Disable-peeling: waiting for reference job results * Libsanitizer: - identified the reason for different behaviour on board and on simulator - proposed a workaround on gcc-patches (qemu-user has a few limitations, so it's desirable to skip some libsanitizer tests) - in the mean time libsanitizer developers received similar concerns from android, and are considering a runtime environment variable to control use of stderr * Neon intrinsics: - resumed investigation on vuzp crc * Internal support == Next == * Peeling: analyze results when available * Revert-coalesce: same * Libsanitizer: reach agreement with upstream * Neon intrinsics: continue with vuzp crc

12 years, 2 months

1
0
0 0

[ACTIVITY] Week 16

by Will Newton

== Progress == * Further work on glibc memcpy IFUNC patch based on review. * Ported libdwarf to aarch64 and submitted upstream. * Disabled gold build in binutils cbuild job and created a gold job. * Investigated binutils testsuite failure on precise. * On leave Friday. == Issues == * None. == Plan == * Submit a patch for binutils testsuite failure on precise. * Complete work on glibc memcpy iFUNC patch. * Follow up binutils IFUNC patch. * AArch64 IFUNC next... -- Will Newton Toolchain Working Group, Linaro

12 years, 2 months

1
0
0 0

[ACTIVITY] 15 - 19 April 2013

by Omair Javaid

== Progress == * Completed investigation of GDB dwarf test suite failures on ARM. Almost all failures will be fixed with small updates to test cases assembly language files. * Checked-out GDB 7.6 branch and did comparison of dwarf test case failures on arm. Some test cases have been updated already and dont need a patch. * Started filtering GDB test suite results on ARM for possible failures due to assembly language incompatibility. * Tried some experimentation with cbuild, and ec2 instances only to find out they are not connected with lab. * Completed Ireland Visa process. Spent Friday and most part of Thursday for the documents attestation, fee submission and postage stuff. *** Still No blue-print available to log work in JIRA. == Plan == * Filter all arm assembly language compatibility updates required to gdb test suite and create a patch. * Get an intro to gdb patch submission process for a possible fix to gdb test suite for arm assembly compatibility. * Start looking into gdb.mi test suite failures on arm. * Fill up the arm native vs arm remote comparison sheet. * Figure out a way to use hackbox for gdb testing on arm.

12 years, 2 months

1
0
0 0

[ACTIVITY] Week 16

by Yvan Roux

== Issues == * None == Progress == * Libunwind AArch64 support: - Implemented signal frame detection routine. - Resuming with signal is failing, debug ongoing. == Plan == * Libunwind AArch64 support: - Fix and submit upstream

12 years, 2 months

1
0
0 0

[ACTIVITY] 15-19 April 2013

by Venkataramanan Kumar

== Progress == Very short week, was doing some AMD internal tasks and attend local meetings. * gprof support work for Aarch64. Not much progress this week. Working on GCC side to support gprof for Aarch64. == Plan == * Continue gprof support work for Aarch64

12 years, 2 months

1
0
0 0

[ACTIVITY] 15-19 April 2013

by Kugan

== Summary == - http://cards.linaro.org/browse/TCWG-13 - performance regression is due to alignment of function. - there is an increase in runtime of core_state_transition even though there is no difference in the code generated with the patch - Adding nops seems to improve the locality and performance; it gets better than without the patch for THUMB2. - Get spec2000 results for http://cards.linaro.org/browse/TCWG-14 to decide on the next step - Couldn’t get SPEC2000 results with CBUILD - set-up spec benchmarks in chromebook and now running locally. - https://blueprints.launchpad.net/gcc-linaro/+spec/better-end-of-loop-counte… - Initial investigation shows that the code generated is same as expected. == Plan == - http://cards.linaro.org/browse/TCWG-13 - follow it up - Get spec2000 results for http://cards.linaro.org/browse/TCWG-14 to decide on the next step - Look for improvement in VRP for zero/sign extension

12 years, 2 months

1
0
0 0

[ACTIVITY] week 16

by Renato Golin

== Progress == * Running around JM/lencode bug - caused by a codegen opt (ICMP fold) that had repercussions only on A9 and A15 code generation - spent three days trying to reduce the case when the problem fixed itself miraculously >:( * Planning for the future - Agreeing on short-term plans for Q2 * Buildbot - Working on self-hosting bot - Moved local buildmaster to hackbox * Investigating LLVMLinux - Building Android kernel with LLVM - Investigating breakage in Debug mode == Plans == * Continue self-hosting bot * Try running a CBuild benchmark with LLVM * Start putting up together the infrastructure for release 3.3 * Try to extract useful information from perf database

12 years, 3 months

1
0
0 0

[ACTIVITY] report week 16

by Peter Maydell

Progress: * qemu maintenance ** sent arm-devs and target-arm pullreqs now we're in softfreeze * VIRT-4 ** received Arndale board, confirmed it works (took several hours mostly due to bonkers power switch design) ** VIRT-49 *** making progress; updated card with a list of sub-subtasks Plans: * keep pushing on with VIRT-49 * finish config of arndale board, test running KVM on it * book travel/hotel for Connect Dublin * office move Fri 26/Mon 29 -- PMM

12 years, 3 months

1
0
0 0

http://cbuild.validation.linaro.org/helpers/recent ISE today

by Matthew Gretton-Dann

All, http://cbuild.validation.linaro.org/helpers/recent was reporting an Internal Server Error earlier today, and after looking at the logs the resultant cause was because the gcc-4.8+svn198079 Lava job (https://validation.linaro.org/lava-server/scheduler/job/52224) decided that it was an a9 (as opposed to a9hf) job and that it didn't no which version of Ubuntu it was running on. The caused the logs to be put in http://cbuild.validation.linaro.org/build/gcc-4.8+svn198079/logs/armv7l--cb… The tcwg-web app then fell over because it couldn't pass the armv7l--cbuild-panda-es06-cortexa9r1 name. I fixed the issue by manually renaming the build log directory to: http://cbuild.validation.linaro.org/build/gcc-4.8+svn198079/logs/armv7l-pre… And once the cron job which scans the builds had run everything now works. Actions: 1. Paul - do you mind taking a look at the build and seeing what went wrong - my initial cursory glance makes me believe its the board having heat issues causing random things to happen. 2. Paul & Matt - Looking at the code (and from something else Michael said to me last week) I think having hostnames with '-' characters in them will confuse the cbuild interface. I propose changing cbuild to do a s/-/_/g on all the hostname it reads as a workaround. I don't plan on changing actual hostnames of boards. Paul is this going to cause a problem for you in Lava? Thanks, Matt -- Matthew Gretton-Dann Toolchain Working Group, Linaro

12 years, 3 months

2
2
0 0

Linaro toolchain Android linking problem redivivus

by Marius Cetateanu

Hi, Some time ago I had some problems linking my project libraries for Android using the Linaro toolchain 4.7.1 which I reported to the list: http://lists.linaro.org/pipermail/linaro-toolchain/2012-June/002631.html I ended up using the 4.6.x version of the compiler because I could not find a fix and I did not get any hints from the mailing list. Now I need to really switch to 4.7(for better C++11 support) but I'm pretty much having the same issue with the 4.7.3 version: E.g. System/Logging/DroidLogger.cpp.o: requires unsupported dynamic reloc R_ARM_REL32; recompile with -fPIC /home/dev/android/android_linaro_toolchain_4.7/bin/../libexec/gcc/arm-linux-androideabi/4.7.3/real-ld: error: /home/marius/Development/ToolChains/Android/experimental_ndk/sources/cxx-stl/gnu-libstdc++/4.7.3/libs/armeabi-v7a/libsupc++.a(eh_globals.o): requires unsupported dynamic reloc R_ARM_REL32; recompile with -fPIC /home/dev/android/android_linaro_toolchain_4.7/bin/../libexec/gcc/arm-linux-androideabi/4.7.3/real-ld: error: hidden symbol '__dso_handle' is not defined locally /home/dev/android/android_linaro_toolchain_4.7/bin/../libexec/gcc/arm-linux-androideabi/4.7.3/real-ld: error: hidden symbol '__dso_handle' is not defined locally I'm using it with the Android NDK version r8e. I have downloaded the prebuilt binaries: android-toolchain 4.7 (ICS, JB) <http://www.linaro.org/downloads/> 4.7-2013.03 13.03 (Linaro GCC 4.7-2013.03) 4.7.3 20130226 (prerelease) Does anyone have any hints on how to overcome the above mentioned problem? -- Marius Cetateanu | Software Engineer T +32 2 888 42 60 F +32 2 647 48 55 E mce(a)softkinetic.com YT www.youtube.com/softkinetic SK Logo <www.softkinetic.com> Boulevard de la Plaine 15, 1050, B-Brussels, Belgium Registration No: RPM/RPR Brussels 0811 784 189 Our e-mail communication disclaimers & liability are available at: www.softkinetic.com/disclaimer.aspx

12 years, 3 months

2
1
0 0

Access to ARM hardware

by Renato Golin

Hi Matt, This week I found an error in LLVM that can only be reproduced on ARM hardware, if the GCC that compiles it specifies --mcpu=cortex-a15. The error is a segfault on one of the tests compiled by that Clang/LLVM. As you can see, it's not something trivial that we'd expect people to do easily. My question is: How do we tackle this type of bug? One option is to do all the debugging and interface with the original patch author until we fix the problem. This works well for simple bugs, but in this case I'm not sure it will work. Another option was to have a board on Linaro's DMZ with no access to anything else internally, so that people could log in and debug the problem in situ. This board would have to be setup just for the debugging with a random password given only to the author of the patch and cleaned up right after the bug is fixed (to avoid external abuse). We could use the same board for LLVM, GCC, GDB, etc. but it should be easy to re-flash it to a minimum system, so that we don't spend too much time setting it up. Does anyone have a better idea? cheers, --renato

12 years, 3 months

1
0
0 0

g++ 4.7.3 ICEs building SNU

by Tom Gall

Hi, Feel free to point me at a newer toolchain. Was building the SNU OpenCL SDK native on my chromebook running ubuntu raring when I hit the following: make: Entering directory `/home/tgall/opencl/SNU/src/runtime/build/cpu' arm-linux-gnueabihf-g++ -fsigned-char -march=armv7-a -mfloat-abi=hard -mfpu=neon -ftree-vectorize -ftree-vectorizer-verbose=0 -fsigned-char -fPIC -DDEF_INCLUDE_ARM -g -c -o smoothstep.o /home/tgall/opencl/SNU/src/runtime/hal/device/cpu/common/smoothstep.c -I/home/tgall/opencl/SNU/inc -I/home/tgall/opencl/SNU/src/runtime/hal/device/cpu -I/home/tgall/opencl/SNU/src/runtime/hal/device/cpu/async -I/home/tgall/opencl/SNU/src/runtime/hal/device/cpu/atomic -I/home/tgall/opencl/SNU/src/runtime/hal/device/cpu/common -I/home/tgall/opencl/SNU/src/runtime/hal/device/cpu/conversion -I/home/tgall/opencl/SNU/src/runtime/hal/device/cpu/geometric -I/home/tgall/opencl/SNU/src/runtime/hal/device/cpu/integer -I/home/tgall/opencl/SNU/src/runtime/hal/device/cpu/math -I/home/tgall/opencl/SNU/src/runtime/hal/device/cpu/reinterpreting -I/home/tgall/opencl/SNU/src/runtime/hal/device/cpu/relational -I/home/tgall/opencl/SNU/src/runtime/hal/device/cpu/vector -O0 -g In file included from /home/tgall/opencl/SNU/src/runtime/hal/device/cpu/cl_cpu_ops.h:47:0, from /home/tgall/opencl/SNU/src/runtime/hal/device/cpu/common/smoothstep.c:34: /home/tgall/opencl/SNU/src/runtime/hal/device/cpu/type/cl_ops_floatn.h: In function 'float2 operator-(float, float2)': /home/tgall/opencl/SNU/src/runtime/hal/device/cpu/type/cl_ops_floatn.h:114:1: internal compiler error: output_operand: invalid operand for code 'P' Please submit a full bug report, with preprocessed source if appropriate. See <file:///usr/share/doc/gcc-4.7/README.Bugs> for instructions. Preprocessed source stored into /tmp/cciluYVq.out file, please attach this to your bugreport. Traceback (most recent call last): File "/usr/share/apport/gcc_ice_hook", line 34, in <module> pr.write(open(apport.fileutils.make_report_path(pr), 'w')) File "/usr/lib/python2.7/dist-packages/problem_report.py", line 254, in write self._assert_bin_mode(file) File "/usr/lib/python2.7/dist-packages/problem_report.py", line 632, in _assert_bin_mode assert (type(file) == BytesIO or 'b' in file.mode), 'file stream must be in binary mode' AssertionError: file stream must be in binary mode make: *** [smoothstep.o] Error 1 tgall@miranda:~/opencl/SNU$ arm-linux-gnueabihf-g++ --version arm-linux-gnueabihf-g++ (Ubuntu/Linaro 4.7.2-23ubuntu2) 4.7.3 I've attached the preprocessed source as well. FWIW, I don't hit this when building with -O3. In this case I was compiling for debug. Thanks! -- Regards, Tom "Where's the kaboom!? There was supposed to be an earth-shattering kaboom!" Marvin Martian Tech Lead, Graphics Working Group | Linaro.org │ Open source software for ARM SoCs w) tom.gall att linaro.org h) tom_gall att mac.com

12 years, 3 months

3
2
0 0

[ACTIVITY] 8-12 April 2013

by Christophe Lyon

== Progress == * Disable-peeling: - some benchmarking jobs ran, thanks to the new boards in cbuild. - Spawned other jobs for reference * Libsanitizer: - Built native GCC on snowball to understand the isatty() behaviour compared to qemu. * Neon intrinsics codegen: - resumed looking at the vuzp crc example from Steve Capper. * Neon intrinsics codegen: - added fp16 support (works with RVCT, GCC does not support it yet) * Internal support == Next == * Disable-peeling: analyze results when available. * Revert-coalesce-vars: idem. * Libsanitizer: analyze isatty() on board * Neon intrinsics: continue with vuzp example.

12 years, 3 months

1
0
0 0

[ACTIVITY] Week 15

by Yvan Roux

One day off this week. == Issues == * None == Progress == * Linaro GCC 4.8, 4.7 and 4. 2013.04 released (with CL and MG) * Boehm-gc AArch64 support backport in GCC: - support committed. * Libunwind AArch64 support: - Resumed ongoing work. == Plan == * Libunwind AArch64 support: - Fix and submit upstream

12 years, 3 months

1
0
0 0

[ACTIVITY] 8 - 12 April 2013

by Omair Javaid

== Progress == * Started investigating dwarf test suite failures on ARM. * Created a new comparison between arm native gdb and arm remote gdb. * More investigation of test cases to figure out causes of test cases that are not run or unsupported. * Experimentation with screens on gateway to speed up remote debugging, didnt work. * 1:1 with Matt. * Took a day off on Friday 12th April 2013 for car checkup in workshop. * Received Invitation letter from Arwen on Friday which means now visa application only needs hotel booking information. *** Still No blue-print available to log work in JIRA. == Plan == * Setup arm gdb to debug itself and debug dwarf problems on arm. * Fill up the arm native vs arm remote comparison sheet. * Submit Ireland visa application after receiving invitation letter and hotel booking details. * Setup screens for remote testing using toolchain cbuild infrastructure.

12 years, 3 months

1
0
0 0

[ACTIVITY] 8-12 April 2013

by Venkataramanan Kumar

== Progress == * gc sections tests Completed upstream of g-c section patches after updating review comments. Closed the card associated with the work. http://cards.linaro.org/browse/TCWG-27 * gprof support work for Aarch64 Read gprof internal documents from sourceware.org. Working on GCC side to support gprof for Aarch64. Misc ------ 11-4-2013 was a local holiday. == Plan == * Continue gprof support work for Aarch64 * Attend internal team meetings on 16 and 17th.

12 years, 3 months

1
0
0 0

[ACTIVITY] 8-12 April 2013

by Kugan

== Summary == - http://cards.linaro.org/browse/TCWG-14 Coremark ARM mode gives about 2% performance improvement with about 1% code size reduction. Thumb2 mode however has performance regression even though code size reduces about 0.6%. Performance regression here is like what we are seeing in EPILOGUE_UESES changes(http://cards.linaro.org/browse/TCWG-13). Spawned spec in CBUILD to see the impact with spec2000. - http://cards.linaro.org/browse/TCWG-13 Thumb2 mode performance regression is due to the percentage of time spent in core_state_transition. Looks like an alignment issue; same asm is generated for this function with the patch. Investigating it. == Plan == - Plan to resolve http://cards.linaro.org/browse/TCWG-13 this week. - Get spec2000 results for http://cards.linaro.org/browse/TCWG-14 to decide on the next step

12 years, 3 months

1
0
0 0

[ACTIVITY] Week 15

by Will Newton

== Progress == * Setting up Chromebook with Ubuntu 13.04. * Developing patch to integrate new memcpy into glibc with IFUNC. * Debugging and submitting a patch for linker issue with IFUNC. == Issues == * None. == Plan == * Get newlib mempcy patch accepted. * Follow up memcpy in bionic. * Submit memcpy IFUNC patch to glibc list. * Get binutils tests into cbuild. -- Will Newton Toolchain Working Group, Linaro

12 years, 3 months

1
0
0 0

[ACTIVITY] report week 15

by Peter Maydell

Progress: * qemu maintenance ** rebased qemu-linaro again ** preparing for upstream softfreeze on 15th ** review virtio patches and anything else that needs attention pre-freeze ** scan of buglist; provided analysis of problem for LP:1090038, closed a few stale bugs ** fixed a bug in an edgecase in fused multiply-accumulate emulation * VIRT-4 [Guest migration support for KVM] ** VIRT-51 *** patches committed upstream, work item complete ** VIRT-73 *** updated Juan's patches to use VMState for ARM CPU migration, fixed a few bugs noted along the way, submitted upstream [work item now just pending review & commit] Plans: * qemu maintenance * VIRT-4 ** VIRT-49 -- PMM

12 years, 3 months

1
0
0 0

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

by Yvan Roux

The Linaro Toolchain Working Group is pleased to announce the 2013.04 release of Linaro GCC 4.8, Linaro GCC 4.7 and Linaro GCC 4.6. Linaro GCC 4.8 2013.04 is the first release in the 4.8 series. Based off the latest GCC 4.8.0+svn197294 release, it includes performance improvements and bug fixes. Interesting changes include: * Our first 4.8 based release * Updates to GCC 4.8.0+svn197294 * Initial optimized support for Cortex-A53 for arm*-*-* targets * Improved support for new ARMv8-A instructions for arm*-*-* and aarch64*-*-* targets. * Backport of optimizations concerning whether to use Neon for 64-bit bitops for arm*-*-* targets. Linaro GCC 4.7 2013.04 is the thirteenth and last development release in the 4.7 series before entering maintenance. Based off the latest GCC 4.7.2+svn197188 release, it includes ARM-focused performance improvements and bug fixes. Interesting changes include: * Updates to GCC 4.7.2+svn197188 * Includes arm/aarch64-4.7-branch up to svn revision 196381 * Backport vectorizer cost model * Turn off 64-bit Bitops in Neon Linaro GCC 4.6 2013.04 is the 26th release in the 4.6 series. Based off the latest GCC 4.6.3+svn197511 release, this is the thirteenth release after entering maintenance and the last regular one. Interesting changes include: * Updates to 4.6.3+svn197511 The source tarballs are available from: https://launchpad.net/gcc-linaro/+milestone/4.8-2013.04 https://launchpad.net/gcc-linaro/+milestone/4.7-2013.04 https://launchpad.net/gcc-linaro/+milestone/4.6-2013.04 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 pages: https://launchpad.net/gcc-linaro/4.8/4.8-2013.04 https://launchpad.net/gcc-linaro/4.7/4.7-2013.04 https://launchpad.net/gcc-linaro/4.6/4.6-2013.04 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, 3 months

1
0
0 0

cbuild binutils job

by Will Newton

Hi all, Currently the binutils job that gets run via cbuild configures with --enable-gold. I guess this could be useful to ensure the gold build is not broken, but has the downside of slowing down the build and causing make check to fail. I propose we do not enable gold until such a time as we wish to formally support gold and fix the broken make check. Does anybody have any objections to doing that? Thanks, -- Will Newton Toolchain Working Group, Linaro

12 years, 3 months

2
1
0 0

[PATCH] libhadoop: CRC: ARM NEON support.

by Steve Capper

Hello linaro-toolchain, This is a patch to add a NEON optimised buffer folding routine to Hadoop 2.0.2-alpha. It allows for faster CRC32c checksum computation. The code is in the form of NEON intrinsics, and details of the implementation can be found at: https://wiki.linaro.org/LEG/Engineering/CRC This patch is against Hadoop 2.0.2-alpha: https://github.com/apache/hadoop-common/tree/branch-2.0.2-alpha I've sent this to linaro-toolchain because I would like the NEON intrinsic implementation to be scrutinised. I would be particularly interested in any superfluous instructions being identified or any bad practices that could be cleaned up before opening these patches up more. Any comments/critique would really be appreciated. Thanks, -- Steve Signed-off-by: Steve Capper <steve.capper(a)linaro.org> --- .../hadoop-common/src/JNIFlags.cmake | 2 + .../native/src/org/apache/hadoop/util/bulk_crc32.c | 142 +++++++++++++++++++- 2 files changed, 142 insertions(+), 2 deletions(-) diff --git a/hadoop-common-project/hadoop-common/src/JNIFlags.cmake b/hadoop-common-project/hadoop-common/src/JNIFlags.cmake index aba4c18..5c9336a 100644 --- a/hadoop-common-project/hadoop-common/src/JNIFlags.cmake +++ b/hadoop-common-project/hadoop-common/src/JNIFlags.cmake @@ -36,6 +36,8 @@ endif (JVM_ARCH_DATA_MODEL EQUAL 32) # Determine float ABI of JVM on ARM Linux if (CMAKE_SYSTEM_PROCESSOR MATCHES "^arm" AND CMAKE_SYSTEM_NAME STREQUAL "Linux") + message("Enabling NEON support.") + set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -mfpu=neon") find_program(READELF readelf) if (READELF MATCHES "NOTFOUND") message(WARNING "readelf not found; JVM float ABI detection disabled") diff --git a/hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/util/bulk_crc32.c b/hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/util/bulk_crc32.c index 8822b5c..6282c60 100644 --- a/hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/util/bulk_crc32.c +++ b/hadoop-common-project/hadoop-common/src/main/native/src/org/apache/hadoop/util/bulk_crc32.c @@ -41,6 +41,16 @@ static inline uint32_t crc_val(uint32_t crc); static uint32_t crc32_zlib_sb8(uint32_t crc, const uint8_t *buf, size_t length); uint32_t crc32c_sb8(uint32_t crc, const uint8_t *buf, size_t length); +#ifdef __ARM_NEON__ +#include <arm_neon.h> +static uint32_t crc32c_neon(uint32_t crc, const uint8_t *buf, size_t length); +#undef USE_PIPELINED +#define CRC32C_FUNC crc32c_neon +#else +#define CRC32C_FUNC crc32c_sb8 +#endif /* __ARM_NEON__ */ + + #ifdef USE_PIPELINED static void pipelined_crc32c(uint32_t *crc1, uint32_t *crc2, uint32_t *crc3, const uint8_t *p_buf, size_t block_size, int num_blocks); #endif @@ -58,7 +68,7 @@ int bulk_calculate_crc(const uint8_t *data, size_t data_len, crc_update_func = crc32_zlib_sb8; break; case CRC32C_POLYNOMIAL: - crc_update_func = crc32c_sb8; + crc_update_func = CRC32C_FUNC; break; default: return -EINVAL; @@ -100,7 +110,7 @@ int bulk_verify_crc(const uint8_t *data, size_t data_len, do_pipelined = 1; #endif } else { - crc_update_func = crc32c_sb8; + crc_update_func = CRC32C_FUNC; } break; default: @@ -256,6 +266,134 @@ static uint32_t crc32_zlib_sb8( return crc; } +#ifdef __ARM_NEON__ + +/* + * Functions to reduce the size of the input buffer (fold) on ARM + * NEON. The smaller buffer has the same CRC32c checksum as the + * original. + * + * Most of the NEON buffer folding work takes place in the function + * below. We do the following: + * 1) 4 sets of vmull.p8's + * 2) Combine these to give a "vmull.p32" (lf3) + * 3) Shift left 1 bit to account for the endianess of multiplication. + * + * The folding and multiplication logic can be found documented at: + * https://wiki.linaro.org/LEG/Engineering/CRC + */ +static inline uint64x1_t crc32c_neon_proc_part(poly8x8_t lhs, poly8x8_t rhs1, + poly8x8_t rhs2, poly8x8_t rhs3, poly8x8_t rhs4) +{ + poly16x8_t lm1, lm2, lm3, lm4; + poly16x4x2_t lz1, lz2; + uint16x4_t le1, le2; + uint32x2_t le3; + uint32x4_t ls1, ls2, lf1, lf2; + uint64x2_t ls3, le4; + uint64x1_t lf3, lf4; + + lm1 = vmull_p8(lhs, rhs1); + lm2 = vmull_p8(lhs, rhs2); + lz1 = vuzp_p16(vget_low_p16(lm2), vget_high_p16(lm2)); + le1 = veor_u16(vreinterpret_u16_p16(lz1.val[0]), + vreinterpret_u16_p16(lz1.val[1])); + ls1 = vshll_n_u16(le1, 8); + lf1 = veorq_u32(ls1, vreinterpretq_u32_p16(lm1)); + + lm3 = vmull_p8(lhs, rhs3); + lm4 = vmull_p8(lhs, rhs4); + lz2 = vuzp_p16(vget_low_p16(lm4), vget_high_p16(lm4)); + le2 = veor_u16(vreinterpret_u16_p16(lz2.val[0]), + vreinterpret_u16_p16(lz2.val[1])); + ls2 = vshll_n_u16(le2, 8); + lf2 = veorq_u32(ls2, vreinterpretq_u32_p16(lm3)); + + le3 = veor_u32(vget_low_u32(lf2), vget_high_u32(lf2)); + ls3 = vshll_n_u32(le3, 16); + le4 = veorq_u64(ls3, vreinterpretq_u64_u32(lf1)); + lf3 = vreinterpret_u64_u32(veor_u32(vget_low_u32(vreinterpretq_u32_u64(le4)), + vget_high_u32(vreinterpretq_u32_u64(le4)))); + lf4 = vshl_n_u64(lf3, 1); + return lf4; +} + +static uint32_t crc32c_neon(uint32_t crc, const uint8_t *buf, size_t length) { + poly8x8_t xor_constant, lhs1, lhs2, lhs3, lhs4, rhs1, rhs2, rhs3, rhs4; + poly8x16_t lhl1, lhl2; + + uint64_t residues[4]; + uint32_t loop; + + if (length % 32) + return crc32c_sb8(crc, buf, length); + + /* + * because crc32c has an initial crc value of 0xffffffff, we need to + * pre-fold the buffer before folding begins proper. + * The following constant is computed by: + * 1) finding a 8x32 bit value that gives a 0xffffffff crc (with initial value 0) + * (this will be 7x32 bit 0s and 1x32 bit constant) + * 2) run a buffer fold (with 0 xor_constant) on this 8x32 bit value to get the + * xor_constant. + */ + xor_constant = vcreate_p8(0x3E43E474A2870290); + + if (crc != 0xffffffff) + return crc32c_sb8(crc, buf, length); + + /* k1 = x^288 mod P(x) - bit reversed */ + /* k2 = x^256 mod P(x) - bit reversed */ + + rhs1 = vcreate_p8(0x510AC59A9C25531D); /* k2:k1 */ + rhs2 = vcreate_p8(0x0A519AC5259C1D53); /* byte swap */ + rhs3 = vcreate_p8(0xC59A510A531D9C25); /* half word swap */ + rhs4 = vcreate_p8(0x9AC50A511D53259C); /* byte swap of half word swap */ + + lhl1 = vld1q_p8((const poly8_t *) buf); + lhl2 = vld1q_p8((const poly8_t *) buf + 16); + + lhs1 = vget_low_p8(lhl1); + lhs2 = vget_high_p8(lhl1); + lhs3 = vget_low_p8(lhl2); + lhs4 = vget_high_p8(lhl2); + + /* pre-fold lhs4 */ + lhs4 = vreinterpret_p8_u16(veor_u16(vreinterpret_u16_p8(lhs4), + vreinterpret_u16_p8(xor_constant))); + + for(loop = 0; loop < (length - 32)/32; ++loop) { + uint64x1_t l1f4, l2f4, l3f4, l4f4; + + l1f4 = crc32c_neon_proc_part(lhs1, rhs1, rhs2, rhs3, rhs4); + l2f4 = crc32c_neon_proc_part(lhs2, rhs1, rhs2, rhs3, rhs4); + l3f4 = crc32c_neon_proc_part(lhs3, rhs1, rhs2, rhs3, rhs4); + l4f4 = crc32c_neon_proc_part(lhs4, rhs1, rhs2, rhs3, rhs4); + + lhl1 = vld1q_p8((const poly8_t *) (buf + 32 * (loop + 1))); + lhl2 = vld1q_p8((const poly8_t *) (buf + 32 * (loop + 1) + 16)); + + __builtin_prefetch(buf + 32 * (loop + 2)); + + lhs1 = vget_low_p8(lhl1); + lhs2 = vget_high_p8(lhl1); + lhs3 = vget_low_p8(lhl2); + lhs4 = vget_high_p8(lhl2); + + lhs1 = vreinterpret_p8_u64(veor_u64(vreinterpret_u64_p8(lhs1), l1f4)); + lhs2 = vreinterpret_p8_u64(veor_u64(vreinterpret_u64_p8(lhs2), l2f4)); + lhs3 = vreinterpret_p8_u64(veor_u64(vreinterpret_u64_p8(lhs3), l3f4)); + lhs4 = vreinterpret_p8_u64(veor_u64(vreinterpret_u64_p8(lhs4), l4f4)); + } + + vst1q_p8((poly8_t *) &residues[0], vcombine_p8(lhs1, lhs2)); + vst1q_p8((poly8_t *) &residues[2], vcombine_p8(lhs3, lhs4)); + + return crc32c_sb8(0, (const uint8_t *)residues, 32); +} + +#endif /*__ARM_NEON__ */ + /////////////////////////////////////////////////////////////////////////// // Begin code for SSE4.2 specific hardware support of CRC32C /////////////////////////////////////////////////////////////////////////// -- 1.7.9.5

12 years, 3 months

1
0
0 0

[ACTIVITY] 1 - 5 April 2013

by Omair Javaid

== Progress == * Investigated gdb test cases that are failing on arm-remote gdbserver configuration. -- Fixed some failures by updating host cross compiler version -- Fixed some failures by fixing environment issue where not being loaded properly. -- All test cases that need to build a shared library and transfer it to remote target FAIL due to problems which seems like dejaganu limitations. * Ran GDB test suite on x86_64 remote gdbserver configuration and compared performance of same configuration on arm. * Got most documentation ready for Ireland Visa application, still waiting on invitation letter and hotel booking details. *** Still No blue-print available to log work in JIRA. == Plan == * Investigate compiler version specific and general failures on arm remote gdbserver configuration. * Start on investigation/fixing of arm specific failures in gdb test suite results. * Submit Ireland visa application after receiving invitation letter and hotel booking details. * Planned Holiday -- Planned Day off on Friday 12th April 2013 for car checkup in workshop.

12 years, 3 months

1
0
0 0

[ACTIVITY] 2 - 5 Apr 2013

by Kugan

== Summary == - benchmarking coremark with VRP based extension elimination * extension elimination in some cases affecting other optimizations * With this improvements are marginal (details below) == Plan == - study crc where extension elimination is resulting in bad code - Find a solution ==Details== If an assignment gimple statement has RHS expression value that can fit in LHS type, truncation is redundant. Zero/sign extensions are redundant in this case and rtl statement can be replaced as from: (insn 12 11 0 (set (reg:SI 110 [ D.4128 ]) (zero_extend:SI (subreg:HI (reg:SI 117) 0))) c5.c:8 -1 (nil)) to: (insn 12 11 0 (set (subreg/s/u:HI (reg:SI 110 [ D.4128 ]) 0) (subreg:HI (reg:SI 117) 0)) c5.c:8 -1 (nil)) With this change, for the following case: short unPack( unsigned char c ) { /* Only want lower four bit nibble */ c = c & (unsigned char)0x0F ; if( c > 7 ) { /* Negative nibble */ return( ( short )( c - 16 ) ) ; } else { /* positive nibble */ return( ( short )c ) ; } } asm without elimination unPack: @ args = 0, pretend = 0, frame = 0 @ frame_needed = 0, uses_anonymous_args = 0 @ link register save eliminated. and r0, r0, #15 cmp r0, #7 subhi r0, r0, #16 uxthhi r0, r0 sxth r0, r0 bx lr .size asm with elimination unPack: @ args = 0, pretend = 0, frame = 0 @ frame_needed = 0, uses_anonymous_args = 0 @ link register save eliminated. and r0, r0, #15 cmp r0, #7 subhi r0, r0, #16 sxth r0, r0 bx lr In some cases, changed rtl statement is not eliminated by later passes and is generated as a mov instruction. Worse, it also seems to affect the other optimization passes and resulting in worse code for crc. Not found the cause for it yet.

12 years, 3 months

1
0
0 0

[ACTIVITY] 1 - 5 Apr 2013

by Venkataramanan Kumar

== Progress == * gc sections tests Completed adding gc-section test cases. 1. TLS and GOT tests. http://sourceware.org/ml/binutils/2013-03/msg00273.html 2. PLT tests. http://sourceware.org/ml/binutils/2013-03/msg00273.html * Evaluate gprof work. There is one function hook "find_call" which is machine dependent and is written for i386.c/sparc Then there are changes in configure.in to add architecture details. * 1-1 with Matt. == Plan == Continue gprof support work for Aarch64

12 years, 3 months

1
0
0 0

[ACTIVITY] Week 14

by Renato Golin

== Progress == * Buildbots - All ARM build-bots GREEN! Hurray!!! :D - Improving sort comparison functions makes output reproducible on all machines - Fixed fpcmp, which fixes sqlite3 report - A bad commit broke lots of tests, reverted - Adding a self-hosting check-all Pandaboard - In theory, it works, but config is not perfect yet * Arndale - Suse image is not stable enough, installed Linaro (325) - Fathi got GCC bootstrapping with it, should work - Installed a heat-sink on the board, should reduce problems - Still got network issues, may be the mac address - Someone could liaise with Dave Pigott to get a new MAC on the DHCP * EuroLLVM 2013 - Badges, finishing touches == Plan == * Holidays next week, then * Check with Galina about Beagle bots * Finish Panda self-host + test-suite A9 bot * Gather info and hardware for 3.3 release tests * Plan for the future!

12 years, 3 months

1
0
0 0

[ACTIVITY] Week 14

by Will Newton

== Progress == * Short week (2 days) * Tested memcpy on big endian. * Updated newlib memcpy patch. * More digging into glibc IFUNC. == Issues == * None. == Plan == * Try and get newlib mempcy patch accepted. * IFUNC... -- Will Newton Toolchain Working Group, Linaro

12 years, 3 months

1
0
0 0

[ACTIVITY] Week 14

by Yvan Roux

== Issues == * None == Progress == * Boehm-gc AArch64 support backport in GCC: - Ping maintainers, no response yet. * Libunwind AArch64 support: - No significant improvements, task preempted by review roster. * Merge request review roster: - Lots of reviews done and ongoing to prepare 4.6, 4.7 en 4.8 releases. == Plan == * Libunwind AArch64 support: - Fix and submit upstream.

12 years, 3 months

1
0
0 0

[ACTIVITY] 2-5 April 2013

by Christophe Lyon

== Progress == * Disable-peeling: - Still waiting for the results from cbuild. Because of many merges (pre-release week), there are a lot of jobs in the queue :-( * Libsanitizer: - tried to understand why isatty(2) returns true when executing the testsuite via qemu. * Neon intrinsics codegen: - benchmarking in bare-machine shows that GCC is actually ~5% faster than RVCT on this sample codec. - to be further discussed internally * Neon intrinsics testsuite: - looking at FP16 support. * Turnoff 64bits ops in Neon: - backport in 4.8 done by Matt during the release merges. * Arndale: a few attempts to use it, but it's still unstable. * Internal support == Next == * Disable-peeling: Analyze bench results when available. * Revert-coalesce-vars: Analyze bench results when available. * Libsanitizer: contine isatty(2) study wrt qemu/expect. * Neon intrinsics: check internally for other codecs

12 years, 3 months

1
0
0 0

[ACTIVITY] report week 14

by Peter Maydell

[short week, two days] Progress: * qemu maintenance ** arm-devs pull request (and associated code review, etc) * VIRT-4 [Guest migration support for KVM] ** VIRT-49: implement cp15 sync with kernel *** some forward motion, but partway through realised some work I thought had been committed last year hadn't been, so: ** VIRT-73 *** new work item, covering updating the migration state for the CPU itself to use VMState structures, by updating, testing and tweaking some patches from Juan Quintela from last year *** have done the 'update' part; tests and tweaks still todo -- PMM

12 years, 3 months

1
0
0 0

[ACTIVITY] Week 14

by Zhenqiang Chen

Summary: * Investigate conditional compare. Details: 1. Expand conditional compare as TRUTH_AND_EXPR/TRUTH_IOR_EXPR for tests. 2. Test tree-level changes for conditional compare. * Fix/workaround most ICE issues in regression tests. * Still some fails which expected VRP can optimize the cases. 3. Try to build Coremark and find that conditional compare does block optimizations, which leads to worse performance. Plan: * Investigate VRP and other optimizations to handle conditional compare. * Raise the propose for upstream discussion. Planned leaves: * April 4-8: Chinese Ching Ming Festival and annual leaves. * April 12: Internal team event. * April 16-17: Internal training. Best Regards! -Zhenqiang

12 years, 3 months

1
0
0 0

[ACTIVITY] 25 - 29 March 2013

by Omair Javaid

== Progress == Started investigating gdb test cases that are failing on arm-remote gdbserver configuration. Completed investigation on all timeout gdb test cases failures in arm-remote gdbserver configuration. Setup a ubuntu test machine for gdb testing on x86_64 in remote gdbserver configuration. Initiated visa process for Ireland and sent requests for required documents to Arwen. *** No blue-print available to log work in JIRA. == Plan == Complete investigation of all failure gdb test cases on arm-remote gdbserver configuration. Run gdb test suite in x86_64 remote gdbserver configuration and compare with all other configurations already tested including arm remote to figure out any similar failures while running test suite remotely on two different machines. Book travel to Ireland and complete visa process.

12 years, 3 months

1
0
0 0

[ACTIVITY] Week 13

by Zhenqiang Chen

Summary: * Investigate how to expand conditional compare. Details: 1. Try to expand conditional compare to RTL * It seams hard to expand conditional compare to just one cond_exec insn during expand, since it has to know the cc (GT, LT, etc) set from previous instruction and tell the later instruction which cc (GT, LT, etc) it set. * Try to add new RTL key-word and insn pattern. 2. Follow up Linaro toolchain binaries bug in Yocto build: 1159392, 1161348 and 1161351. Plan: * Generate asm for conditional compare. Planned leaves: * April 4-8: Chinese Ching Ming Festival and annual leaves. * April 12: Internal team event. * April 16-17: Internal training. Best Regards! -Zhenqiang

12 years, 3 months

2
1
0 0

[ACTIVITY] 25-29 March 2013

by Venkataramanan Kumar

== Progress == - Very short work week. I was on leave last Wednesday and Thursday (27th and 28th). - Posted patch for gc-section tests for TLS and got related relocs. - Discussing with Marcus on patch I wrote for gc section tests on PLT related relocs. == Plan == - Post patch for gc section tests for PLT relocs. - Complete gc section tests for other generic cases. - Understand and evaluate gprof support work for Aarch64

12 years, 3 months

1
0
0 0

[ACTIVITY] 25-28 March 2013

by Kugan

== Progress == working on http://cards.linaro.org/browse/TCWG-14 - All but 2 test cases are passing and extension elimination for the simple cases are eliminated - one of the test failure was due to bug with value range propagation pass. Have to investigate this further. - In one instance even though extensions are removed, 1 more instruction is generated (for crc) - Need to investigate it - Got the chromebook and Set up Ubuntu; boot strapping gcc now == Plan == - Start with the benchmarking - investigate the performance and VRP issue - Also start with http://cards.linaro.org/browse/TCWG-13 in parallel

12 years, 3 months

1
0
0 0

[ACTIVITY] Week 13

by Yvan Roux

== Issues == * None == Progress == * Libunwind AArch64 support: - Most of the testsuite is now fine - but some fixes still needed before upstream submission. == Plan == * Libunwind AArch64 support: - Fix and submit upstream.

12 years, 3 months

1
0
0 0

[ACTIVITY] 25-29 March 2013

by Christophe Lyon

== Progress == * Disable-peeling: - benchmarked locally on snowball. Observed a few regressions in spec2k. To be analyzed and confirmed with the results from cbuild. - patched cbuild to work-around a bzr bug which prevented these jobs from being spawned. * Libsanitizer: sent patch upstream. Discussion about interactions with qemu. * Revert-coalesce: spawned thought-to-be reference jobs for benchmarking. * Neon intrinsics codegen: - First analysis of sample codecs seems to indicate that gcc generates sequences of interdependent instructions where rvct manages to insert some code in between. - To be confirmed by dedicated benchmarking, probably in bare-machine mode. * Neon intrinsics testsuite: - Added support for polynomial variants (*_p8, *_p16) - Identified wrong code generated by gcc-linaro-4.7; did not check with trunk. - Transforming into a dejagnu forms will probably be a lot of work :-( * Internal activities == Next == * Disable-peeling: - analyze bench results from cbuild when available - compare with the results from my snowball * Libsanitizer: - resume investigation about isatty problem when ran under qemu. * Turnoff 64bits ops In Neon: - backport in linaro-4.8 once the process has been clarified. * Revert-coalesce: - check bench results * Neon intrinsics codegen: - perform dedicated benchmarking

12 years, 3 months

1
0
0 0

[ACTIVITY] Week 13

by Will Newton

== Progress == * Booked flight for LCE. * Benchmarked and ran tests on new memcpy implementation. * Attempted but failed to get new memcpy tested on big endian (still todo). * Committed new memcpy implementation to cortex strings. * Passed new memcpy to Android team for bionic. * Submitted newlib patch for new memcpy. * Committed binutils ld-elfvsb testsuite fixes, native testsuite now green! * Further investigation of IFUNC in glibc. == Issues == * Pandaboard ES still a bit flakey, Chromebook hopefully on its way to replace it. == Plan == * Iron out issues with native binutils make check in cbuild/LAVA. * Get newlib memcpy patch committed. * Investigate testing memcpy on big endian (qemu user, models?). * IFUNC... -- Will Newton Toolchain Working Group, Linaro

12 years, 3 months

1
0
0 0

[ACTIVITY] report week 13

by Peter Maydell

Progress: * qemu maintenance ** https://ci.linaro.org/jenkins/job/qemu-ltp/ now shows graphs of LTP test results for linux-user mode ** rebased qemu-linaro and got it working again (omap3 display code needed rework after upstream changes) ** investigated why Christoffer Dall's kernels weren't booting: turns out to be that vexpress now requires CONFIG_REGULATOR but doesn't force it to be set or set it in the vexpress_defconfig ** rebased/resent/pinged various in-flight patches * VIRT-4 [Guest migration support for KVM] ** VIRT-49: implement cp15 sync with kernel *** located my work on this from last year, refreshed my memory on how far I'd got and what I was planning to do -- PMM

12 years, 3 months

1
0
0 0

[ACTIVITY] week 13

by Renato Golin

== Progress == * Re-installed the panda buildbot, using USB drive as bot dir * Reviewing lots of ARM patches (more than usual) * Trying Arndale again, some errors, some passes, cooler might be responsible - Got one internal error, one build error and one pass with Ubuntu kernel + patch - Trying Suse image: - It has a broken serial driver (makes things much harder) - sshd does not start by default (in conjunction with serial bug, it's a killer) - Now running on a precarious mode, hopefully enough for our needs * sqlite3 error due to VMUL.f64 while on x86_64 "long double" is f128 - sqlite3 is the best example on what NEVER to do with floating point values >:| - Sent patch, working around TILE-Gx issues == Issues == * Still a bit ill, productivity reduced * Not having a wired network on my desk wastes a LOT of my time == Plan == * Push the sqlite3 patch though * Continue fixing the 4 remaining broken tests * Continue with Arndale investigation with Christophe and Zhenqiang

12 years, 3 months

1
0
0 0

GCC bootstrap on Arndale

by Renato Golin

Hi folks, I'm trying again the bootstrap of GCC on Arndale and it goes pretty well until it has to install libgcc that it just compiled. When I build first time, I get an error while installing libgcc: make[4]: Entering directory `/home/linaro/devel/gcc/build/objs/armv7l-unknown-linux-gnueabihf/libgcc' /bin/bash /home/linaro/devel/gcc/src/libgcc/../mkinstalldirs ../.././gcc (...) /bin/bash /home/linaro/devel/gcc/src/libgcc/../mkinstalldirs ../.././gcc; /usr/bin/install -c -m 644 ./libgcc_s.so.1 ../.././gcc/libgcc_s.so.1; rm -f ../.././gcc/libgcc_s.so; /usr/bin/install -c -m 644 ./libgcc_s.so ../.././gcc/libgcc_s.so Live child 0x01dec548 (install-shared) PID 4405 Reaping losing child 0x01dec548 PID 4405 make[4]: *** [install-shared] Error 1 Though, if I run that command by hand, it works... I then re-ran make and the first point there is an error is on gmp: This program built for arm-unknown-linux-gnueabihf Reading makefiles... Reading makefile `Makefile'... Reaping losing child 0x01866320 PID 4784 make[3]: *** [config.h] Error 1 Removing child 0x01866320 PID 4784 from chain. make[3]: Leaving directory `/home/linaro/devel/gcc/build/objs/gmp' Need a job token; we have children Duplicate the job FD Live child 0x00ae17f8 (all-stage1-libiberty) PID 4755 Live child 0x00be3508 (all-stage1-gmp) PID 4736 Reaping losing child 0x00be3508 PID 4736 make[2]: *** [all-stage1-gmp] Error 2 Removing child 0x00be3508 PID 4736 from chain. Released token for child 0x00be3508 (all-stage1-gmp). make[2]: *** Waiting for unfinished jobs.... Live child 0x00ae17f8 (all-stage1-libiberty) PID 4755 I can't notice anything wrong on gmp (all objects are there), other than a number of symlinks to a missing directory: gmp-mparam.h -> /home/linaro/devel/gcc/src/gmp/mpn/generic/gmp-mparam.h the directory "generic" doesn't exist, and lots of files in "mpn" also point there. Could be a red herring, though. Any ideas? cheers, --renato PS: this doesn't look like an Arndale specific bug, so we might still be able to use them for GCC bootstrapping...

12 years, 3 months

3
3
0 0

[PATCH][for-danny] external-linaro-toolchain-versions: OE variables need to be properly expanded

by Denys Dmytriyenko

From: Denys Dmytriyenko <denys(a)ti.com> Otherwise eglibc version is set to UNKNOWN. Similar fix is already in master. Signed-off-by: Denys Dmytriyenko <denys(a)ti.com> --- conf/distro/include/external-linaro-toolchain-versions.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/distro/include/external-linaro-toolchain-versions.inc b/conf/distro/include/external-linaro-toolchain-versions.inc index 6b5a6fb..8e2c68c 100644 --- a/conf/distro/include/external-linaro-toolchain-versions.inc +++ b/conf/distro/include/external-linaro-toolchain-versions.inc @@ -43,7 +43,7 @@ def elt_get_libc_version(d): if not syspath: return 'UNKNOWN' - libpath = syspath + '/libc/lib/${ELT_TARGET_SYS}/' + libpath = syspath + bb.data.expand('/libc/lib/${ELT_TARGET_SYS}/', d) if os.path.exists(libpath): for file in os.listdir(libpath): -- 1.8.1.5

12 years, 3 months

1
0
0 0

[ACTIVITY] Week 12

by Zhenqiang Chen

Summary: * Send out shrink-wrap related patches for review. * Investigate how to add a new tree code. Details: 1. Fix lp:1157050 and lp:1107659 for Linaro toolchain binaries. 2. Test shrink-wrap dwarf/unwind info and send out the patches for review. 3. Make progress on conditional compare support. With some hard-codes in gcc, it can gimplify a small case to conditional compare on tree and no assert until expand. Plan: * Investigate how to expand conditional compare GIMPLE to RTL and emit asm. Planned leaves: * March 31. * April 4-8. Best Regards! -Zhenqiang

12 years, 3 months

3
4
0 0

Testing binutils natively

by Will Newton

Hi all, I'd like to run the binutils testsuite in a native configuration regularly to find any regressions. Do we have any infrastructure for doing this? It looks like LAVA would be useful but it looks complex and I am not sure if we use that already for running toolchain tests (I think there was a Connect session about that?). Thanks, -- Will Newton Toolchain Working Group, Linaro

12 years, 3 months

3
2
0 0

[ACTIVITY] 18-22 March 2013

by Christophe Lyon

== Progress == * Disable-peeling: - benchmarking locally on snowball - failed to build reference branch on cbuild, for an unknown reason * Turnoff 64bits ops in Neon: - committed upstream in 4.9 (now stage 1) - benches of backport into Linaro-4.7 OK: no significant diff, except +12.6% on spec2k's crafty) - Filed merge request. * Vectorizer cost model: - benches of backport inot Linaro-4.7 OK (no significant diff, as expected). - Filed merge request. * Revert-coalesce: - benches ran in cbuild, but no *-diff.txt file generated. * Libsanitizer: - testsuite results OK. All unsupported tests are normal. * Neon intrinsics codegen: - got internal feedback * GDB reverse debug: - filed 2 bug reports after internal requests. * Misc: - filed several bug reports against cbuild to track the problems I observed. == Next == * Disable-peeling: - analyze bench results - understand/'fix what's wrong with cbuild * Turnoff 64bits ops in Neon: - backport to Linaro-4.8 * Revert-coalesce: - manually compute bench differences if unable to have cbuild do it. * Libsanitizer: - propose patch upstream.

12 years, 3 months

1
0
0 0

[ACTIVITY] 18 - 22 March 2013

by Omair Javaid

== Progress == Knocked out more GDB remote configuration failures that were failing due to timeouts. Had 1:1 with Matt for direction on GDB improvement plan. Looked around for Ireland visa process and filled out visa application. == Plan == Complete review of remote timeout based test case failures. Start work on the GDB improvement blueprint in JIRA from this week. Get remaining documentation for Ireland visa and complete application.

12 years, 3 months

1
0
0 0

[ACTIVITY] 18-22 March 2013

by Venkataramanan Kumar

== Progress == - Looking at TLS relocs and coming up with test cases for garbage collecting them. - Patch for missedout testcases in gc section is up streamed. Thanks to Marcus. == Plan == - Complete gc section test cases for TLS relocs. - Understand and evaluate gprof support work for Aarch64 Misc ----- Leave on Wednesday and Thursday (27th and 28th)

12 years, 3 months

1
0
0 0

[ACTIVITY] 18-22 March 2013

by Kugan

== Progress == - Worked on VRP based zero/sign extension elimination at tree level - Some regression test cases are failing; investigating them == Plan == - Analyse the reason for test case failure and fix them - Extend the code to handle all the possible cases (currently implemented for subset to get the framework working)

12 years, 3 months

1
0
0 0

Regehr: GCC 4.8 Breaks Broken SPEC 2006 Benchmarks

by Mans Rullgard

This post is making the rounds today: http://blog.regehr.org/archives/918 -- Mans Rullgard / mru

12 years, 3 months

4
6
0 0

[ACTIVITY] Week 12

by Yvan Roux

== Issues == * None == Progress == * Libunwind AArch64 support: - basic implementation for building lib and testsuite done - but even a simple test case doesn't work for the moment == Plan == * Libunwind AArch64 support: - continue AArch64 specific implementation and informtation gathering

12 years, 3 months

1
0
0 0

[ACTIVITY] Week 12

by Renato Golin

== Progress == * EuroLLVM paper review * Disabled EH tests on ARM for now * Fixed TSVC: NEON vs. VFP VMUL.f32 (and IEEE 754 correctness) * Changed FeatureNEONForFP to false on EABI ARM targets unless unsafe-math * Trying Arndale again, with u-boot patched, not good * Broken Panda buildbots, trying to fix == Issues == Got ill on Tuesday and only worked partially, if at all, the rest of the week Hopefully will be better next week... == Plan == * Fix our panda buildbot, maybe add more * Final try on Arndale GCC bootstrap before giving up * Continue fixing test-suite failures (only 5 left)

12 years, 3 months

1
0
0 0

[ACTIVITY] report week 12

by Peter Maydell

Progress: * VIRT-4 [Guest migration support for KVM] ** VIRT-51: vexpress migration: ** wrote and submitted patches for all the devices that need fixes ** tracked down a painful bug where the guest just hung on vmload to a missing state-save for a timer device, submitted patch ** remaining work for this item is just responding to patch review -- PMM

12 years, 3 months

1
0
0 0

LLVM ARM NEON VMUL.f32

by Renato Golin

Hi folks, I found an issue while fixing a test using the wrong VMUL.f32, and I'd like to know what should be our choice on this topic that is slightly controversial. Basically, LLVM chooses to lower single-precision FMUL to NEON's VMUL.f32 instead of VFP's version because, on some cores (A8, A5 and Apple's Swift), the VFP variant is really slow. This is all cool and dandy, but NEON is not IEEE 754 compliant, so the result is slightly different. So slightly that only one test, that was really pushing the boundaries (ie. going below FLT_MIN) did catch it. There are two ways we can go here: 1. Strict IEEE compatibility and *only* lower NEON's VMUL if unsafe-math is on. This will make generic single-prec. code slower but you can always turn unsafe-math on if you want more speed. 2. Continue using NEON for f32 by default and put a note somewhere that people should turn this option (FeatureNEONForFP) off on A5/A8 if they *really* care about maximum IEEE compliance. Apple already said that for Darwin, 2 is still the option of choice. Do we agree and ignore this issue? Or for GNU/EABI we want strict conformance by default? GCC uses fmuls... cheers, --renato

12 years, 3 months

5
6
0 0

ARMV8 gcc toolchain issue while compiling for a foundation model

by pavan p m

Hello, I am having an issue with using the gcc toolchain for armv8. I am trying to cross compile a simple program (helloworld.c) as suggested in the link : https://wiki.linaro.org/HowTo/HelloAarch64. But when I try executing the binary on the simulated armv8 (using foundation model), I am getting error in GLIBC, specifically "/lib/libc.so.6: version `GLIBC_2.16' not found" . Could you please help me as to what could be wrong here? Thanks, Pavan

12 years, 3 months

2
2
0 0

[ACTIVITY] 11-15 March 2013

by Will Newton

== Progress == * Analyzed Android kernel linker issue and created LP #1154165 to track it. * Triaged remaining binutils Launchpad tickets. * Setup my Pandaboard with Linaro 13.01 (13.02 oopses on boot) to run tests. * binutils: Committed fix for LP #517081 (Floating-point assembly and disassembly bugs on armel) upstream. * binutils: Committed a fix for ARM EABI tests upstream. * Lots of admin stuff. == Plan == * Get binutils testsuite green in a native configuration (fix LP #812276). * Investigate getting binutils testuite automated via cbuild/Lava. * More bugs... -- Will Newton Toolchain Working Group, Linaro

12 years, 4 months

1
0
0 0

[ACTIVITY] 11 - 15 March 2013

by Omair Javaid

== Progress == Reviewing GDB tests that FAIL due to timeout problems in remote configuration. Made some changes to some of the GDB tests that FAIL on arm targets to check if they work by minor modifications. Sick Days: Had been sick due to cough n fever and a drop in blood pressure made me take most part of Thursday and Friday off. == Plan == Get with Matt for Post- Connect work targets. Review remaining GDB tests that FAIL due to timeout problems in remote configuration. Further experiments with GDB test suite to check support for unsupported tests on arm.

12 years, 4 months

1
0
0 0

Linaro Toolchain Binaries 2013.03 released

by Bernhard Rosenkränzer

The Linaro Toolchain and Platform Working Groups are pleased to announce the 2013.03 release of the Linaro Toolchain Binaries, a pre-built version of Linaro GCC and Linaro GDB that runs on generic Linux or Windows and targets the glibc Linaro Evaluation Build. Uses include: * Cross compiling ARM applications from your laptop * Remote debugging * Build the Linux kernel for your board What's included: * Linaro GCC 4.7 2013.03 * Linaro GDB 7.5 2012.12 * A statically linked gdbserver * A system root * Manuals under share/doc/ The system root contains the basic header files and libraries to link your programs against. Interesting changes include: * gcc updated to 4.7-2013.03: * Updates to GCC 4.7.2+svn196272 * Includes arm/aarch64-4.7-branch up to svn revision 196225 * A fix for LP #1135633: [linaro regression] alsa-tools FTBFS with error "unable to find a register to spill in class ‘AREG’" The Linux version is supported on Ubuntu 10.04.3 and 12.04, Debian 6.0.2, Fedora 16, openSUSE 12.1, Red Hat Enterprise Linux Workstation 5.7 and later, and should run on any Linux Standard Base 3.0 compatible distribution. Please see the README about running on x86_64 hosts. The Windows version is supported on Windows XP Pro SP3, Windows Vista Business SP2, and Windows 7 Pro SP1. The binaries and build scripts are available from: https://launchpad.net/linaro-toolchain-binaries/trunk/2013.03 Need help? Ask a question on https://ask.linaro.org/ Already on Launchpad? Submit a bug at https://bugs.launchpad.net/linaro-toolchain-binaries On IRC? See us on #linaro on Freenode. Other ways that you can contact us or get involved are listed at https://wiki.linaro.org/GettingInvolved.

12 years, 4 months

1
0
0 0

[ACTIVITY] 13-15 March 2013

by Yvan Roux

Short week to ... == Progress == * Configured GCC testsuite to run on the Foundation model. * Boehm GC AArch64 support: - Submitted gc integration patch in GCC upstream for review. - libatomic_ops AArch64 support branch re-tested and merged in mainline. == Next == * AArch64 libunwind support.

12 years, 4 months

1
0
0 0

[ACTIVITY] 11-15 March 2013

by Venkataramanan Kumar

== Progress == - Closed the blue print for gc-sections implementation since the patch got upstreamed. - Opened new blue print for adding more test coverage to gc-sections tests. - Submitted a patch to enable missed out gc-sections test cases from ld-elf group. - Wrote gc-sections test cases for few GOT related relocs. == Plan == - Understand equivalences created during CFG traversal for jump threading. - Look at GCC code for a simple test case where jump threading is missed out. - Continue writing gc-sections test cases for remaining relocs.

12 years, 4 months

1
0
0 0

[ACTIVITY] 12-15 March 2013

by Kugan

== Progress == - Monday was a public holiday - Studied benchmarks and analysed the rtl/asm for redundant sign extensions - Came up with simple test cases based on this (have 6 test cases now) - Looked at gcc tree documentations and helper macros; tried it by adding more debug dumps for types at tree level == Plan == - Start with the algorithm for sign extension elimination - Skipping manual changes at source level/asm level to see the performance improvement for now.

12 years, 4 months

1
0
0 0

[ACTIVITY] 13-15 March 2013

by Christophe Lyon

Short week... == Progress == * Catch up on internal tasks / email that piled up during holidays + Connect * Resumed work on disable-peeling: - local benchmarking on snowball - restarting benchmarks via cbuild for an additional check == Next == * Check benchmark results on disable-peeling * Have a look at how to dejagnu-ize my Neon intrinsic tests * Check results of libsanitizer branch * Check results of 'revert-coalesce' branch * Check bench results of '4.7-backport-vect-cost-model' * Check bench results of '4.7-turnoff-64bits-ops' * Investigate why cbuild did not generate all the comparisons I expected (*-diff.txt files) * Check whether 2013.03 release process exposed the same problems I observed with 2013.02.

12 years, 4 months

1
0
0 0

[ACTIVITY] report week 11

by Peter Maydell

Progress (in a 1 day week...): * qemu maintenance: ** released qemu-linaro 2013.03 ** arm-devs pullreq * VIRT-4 [Guest migration support for KVM] ** audited vexpress code for migration issues: there are a few devices needing minor cleanup, and one (pflash_cfi01) which has no migration support at all and needs it writing * KVM other: ** reviewed virtio-blk refactoring patchset -- PMM

12 years, 4 months

1
0
0 0

[ACTIVITY] Week 11

by Renato Golin

== Progress == * Recuperating from Connect, catching up on email * Attended David's and Maddog's presentation on Monday * Investigating Arndale bug (seems to work with new kernel) - Bootstrapping LLVM works, GCC doesn't * Reviewing patches upstream (Mans', Tim's, others) * Fixed three bugs on test-suite that depended on RNGs - Only two more tests broken only in ARM - Five others broken on both (but only visible on our bot) - Nine EH tests that need disabling, for now == Plan == * Tackle the two last ARM specific bugs * If time allows, clear the other 5 * Try to disable any EH-specific test on ARM * Start talks about getting an internal binary distribution process going

12 years, 4 months

1
0
0 0

lists.linaro.org maintenance completed

by IT Services

This is to let you know that the migration of lists.linaro.org has been successfully completed. As per the email I sent on Wednesday, it may take some time for the new address of the server to be seen by your computer. You can check this by trying to connect to the web site: http://lists.linaro.org/ If you are able to connect and you do not get an error, this means you are connecting to the new server and you can send email to the lists. If you experience any problems after the weekend and you find that you still cannot connect to the server, please reply to this email to let us know. Regards Philip IT Services Manager Linaro

12 years, 4 months

1
0
0 0

Linaro GCC 4.7 and 4.6 2013.03 released

by Matthew Gretton-Dann

The Linaro Toolchain Working Group is pleased to announce the 2013.03 release of both Linaro GCC 4.7 and Linaro GCC 4.6. Linaro GCC 4.7 2013.03 is the twelth release in the 4.7 series. Based off the latest GCC 4.7.2+svn195745 release, it includes ARM-focused performance improvements and bug fixes. Interesting changes include: * Updates to GCC 4.7.2+svn196272 * Includes arm/aarch64-4.7-branch up to svn revision 196225 * A fix for LP #1135633: [linaro regression] alsa-tools FTBFS with error "unable to find a register to spill in class ‘AREG’" Linaro GCC 4.6 2013.02 is the 25th release in the 4.6 series. Based off the latest GCC 4.6.3+svn196247 release, this is the twelth release after entering maintenance. Interesting changes include: * Updates to 4.6.3+svn196247 The source tarballs are available from: https://launchpad.net/gcc-linaro/+milestone/4.7-2013.03 https://launchpad.net/gcc-linaro/+milestone/4.6-2013.03 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 pages: https://launchpad.net/gcc-linaro/4.7/4.7-2013.03 https://launchpad.net/gcc-linaro/4.6/4.6-2013.03 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 -- Matthew Gretton-Dann Toolchain Working Group, Linaro

12 years, 4 months

1
0
0 0

[ANNOUNCE] Linaro QEMU 2013.03 released

by Peter Maydell

The Linaro Toolchain Working Group is pleased to announce the release of Linaro QEMU 2013.03. Linaro QEMU 2013.03 is the latest release of qemu-linaro. Based off upstream (trunk) QEMU, it includes a number of ARM-focused bug fixes and enhancements. This release has been updated to be based on upstream's recent 1.4.0 release. It also includes ARM KVM support patches which are in sync with the ABI as committed to the upstream Linux kernel for 3.9. This feature is still under development but will no longer be subject to kernel-vs-userspace ABI breaks. The source tarball is available at: https://launchpad.net/qemu-linaro/+milestone/2013.03 More information on Linaro QEMU is available at: https://launchpad.net/qemu-linaro -- PMM

12 years, 4 months

1
0
0 0

Planned maintenance - lists.linaro.org

by IT Services

Hello You are receiving this email because you are subscribed to one or more mailing lists provided by the lists.linaro.org server. IT Services are announcing planned maintenance for this server scheduled for *Friday 15th March 2013, starting at 2pm GMT*. The purpose of the work is to move the service to another server. There will be some disruption during this maintenance. In order to ensure that you do not accidentally try to use the service while it is being moved, the current server will be shut down at 2pm. A further email will be sent on Friday afternoon to confirm that the migration of the service is completed. However, due to the way servers are found, it may take a while before your computer is able to connect to the relocated service. After the old server has been shut down, email sent to any of the lists will be queued, but it is possible that the sending server will still trying to deliver the email to the old server rather than the new one when it is started. It is therefore *strongly* recommended that you do not send any email to an @lists.linaro.org email address until you can connect to the new service, which you will be able to test by trying to use a web browser to connect to http://lists.linaro.org after you receive the email confirming that the migration has been completed. Since the old service will be shut down, if you are able to connect, you can be sure you have connected to the new service. If by Monday you are still unable to connect to the service or you are not able to send email to an @lists.linaro.org email address, please send an email to its(a)linaro.org. Thank you. Regards Philip IT Services Manager Linaro

12 years, 4 months

1
0
0 0

compile using -mfloat-abi=soft option

by 서재권

12 years, 4 months

2
1
0 0

4th March 2013 - 8th March 2013

by Omair Javaid

== This Week === * Couldnt help my luck and wasnt able to reach Hong Kong due to delay in visa processing by Hong Kong immigration department. * Remotely attended live streams of Linaro Connect Asia * Tried to reproduce all open bugs under linaro-gdb project on launchpad and created a review sheet. * Created a comparison sheet to figure out why certain gdb tests are failing or not being run in different configurations. == Next week == * Try to enable some native only tests and see if the functionality can be tested for remote configurations as well. * Set out some priority on blue prints and bugs under linaro-gdb project and start with some stuff with higher priority. * Caught some flu over the weekend and still a bit down with fever n headache.

12 years, 4 months

1
0
0 0

[ACTIVITY] report week 10

by Peter Maydell

Progress: * Linaro Connect Asia (Hong Kong) * Lots of discussions with virtualization team (first time we've all been able to meet up!), making sure we all understand our TODO list, priorities, etc, and getting these details written up in JIRA * Presentation of KVM current status and discussion of next steps; we tried to keep the focus on the discussion/audience input part and I thought it was pretty good * Several linked conversations on UEFI and how it boots hypervisors (including KVM); came to a conclusion everybody was happy with (UEFI mostly runs in SVC mode but provides mechanisms so UEFI bootloader code can start the kernel in Hyp mode as it requires); Grant Likely will be moving this forward * KVM/ARM support patchset for QEMU was accepted into upstream this week! * looked at fixing QEMU's totally broken model of the versatile PCI controller -- PMM

12 years, 4 months

1
0
0 0

[ACTIVITY] 25th Feb 2013 - 1st March 2013

by Omair Javaid

== This Week === * Compiled GDB graphical report and test-case statistics out of the results generated by running gdb-test suite in different configurations. * Worked on release testing of QEMU. All configurations mentioned in release template have been tested alongwith an extra configuration of 13.01 ubuntu on vexpress. * Kept running around for my Hong Kong visa which is still not with me. == Next week == * Try to make it to The Connect in Hong Kong or at least attend remotely. * Participate in various activities at The Connect.

12 years, 4 months

1
0
0 0

[ACTIVITY] report week 09

by Peter Maydell

Progress: * qemu-linaro: rolled tarball, sent it off for testing * investigated and reviewed fixes for upstream regressions in ADC/SBC instruction implementation * sent updated versions of various patchsets * fixed review comments on QEMU KVM support patchset, resent * reviewed a pile of ARM patches from other people and sent arm-devs pullreq -- PMM

12 years, 4 months

1
0
0 0

[ACTIVITY] 25 - 28 Feb

by Renato Golin

My taxi arrives in a few hours and I still have to buy the wine, so that's all for me for the week... See you guys in Hong Kong!! == Progress == * Vectorizer - Adding more tests to the global structure vectorizer - http://llvm.org/viewvc/llvm-project?view=revision&revision=175964 - http://llvm.org/viewvc/llvm-project?view=revision&revision=175898 - Adding it to the docs - http://llvm.org/viewvc/llvm-project?view=revision&revision=175965 * LLVM Docs - Changing docs here and there - http://llvm.org/viewvc/llvm-project?view=revision&revision=176096 - http://llvm.org/viewvc/llvm-project?view=revision&revision=176090 - http://llvm.org/viewvc/llvm-project?view=revision&revision=176033 - http://llvm.org/viewvc/llvm-project?view=revision&revision=176209 - http://llvm.org/viewvc/llvm-project?view=revision&revision=176211 * Buildbot - Upgraded Pangolin to Ubuntu 12.10, linaro-panda-01 back to life - Investigating breaks on the build, chasing people around - Trying to fix ARMv5 buildbot - http://llvm.org/viewvc/llvm-project?view=revision&revision=176095 - http://llvm.org/viewvc/llvm-project?view=revision&revision=176219 - http://llvm.org/viewvc/llvm-project?view=revision&revision=176243 - http://llvm.org/viewvc/llvm-project?view=revision&revision=176246 - Creating a way to re-spawn broken bots (still very crude) - Discussing about ways for improving uncertainties on LNT benchmarks - Proposed GSoC project to create regression analysis on results * GCC 4.6.3 - Investigating broken LLVM build on Panda/4.6.3 - O3 breaks differently than O2, O1/O0 doesn't break - Works with 4.7 and 4.6.3 on x86_64 even at O3 - Debug step doesn't show much info (mostly optrimized out) * LAVA - Checking with Dave Piggot why git.linaro.org doesn't work with LAVA - Possibly the way I'm doing (clone of a clone of a clone) == Plan == Connect

12 years, 4 months

1
0
0 0

crosstool-ng

by Kalai Narayanan-SSI

Hi, I got the crosstool-ng from the 2013.02 release and wanted to build the linaro-aarch64-linux-gnu target locally. During the build, I'm encountering errors. I didn't do any menuconfig for the above target before starting the build. I'm seeing the following errors with the first during the ppl build ... [INFO ] Installing PPL [EXTRA] Configuring PPL [ERROR] configure: error: Cannot find GMP version 4.1.3 or higher. [EXTRA] Saving state to restart at step 'cloog'... ... (from build-ppl/config.log .... ... configure:11257: result: no configure:11392: error: Cannot find GMP version 4.1.3 or higher. GMP is the GNU Multi-Precision library: see http://www.swox.com/gmp/ for more information. ....) ... [INFO ] Installing CLooG/ppl [EXTRA] Configuring CLooG/ppl [ERROR] checking for version 0.10 (or later revision) of PPL... configure: error: Can't find correct version of PPL. [EXTRA] Saving state to restart at step 'mpc'... ... (from build-cloog-ppl/cobnfig.log ... ... configure:11237: error: Can't find correct version of PPL. ...) If I'm building a known target with the released version, why am I seeing these errors? Thanks, Kalai

12 years, 4 months

2
3
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain