- linaro-toolchain - lists.linaro.org

[PATCH] Cortex Strings AArch64 optimized implementations of memmove, strlen and strncmp

by Marcus Shawcroft

Folks, This series of patches adds aarch64 specific implementations of memmove, strlen, strncmp to the cortex strings library and the corresponding test cases lifted directly from glibc. Enjoy /Marcus

12 years, 8 months

2
1
0 0

libstdc++6 built from gcc-4.7 missing some symbols for arm-linux-gnueabi

by Matthias Klose

asking for some help about debian #697521 and lp: #1096619. looking at the config.log files for armel/armhf I don't see any differences. I assume it's a difference in the cpu configuration (armv4/v5 vs. armv7) not soft/hard-float. any pointers?

12 years, 8 months

1
0
0 0

[ACTIVITY] 3-4 January 2013

by Yvan Roux

== Progress == * Short week (2 working days) * Merge request review - Merged approved branches * Boehm GC AArch64 support - Back on this topic == Next == * Course leading most of the week * Review roster

12 years, 8 months

1
0
0 0

--no-gnu-unique option to disable STB_GNU_UNIQUE

by naveen yadav

Dear All, Is it possible to disable STB_GNU_UNIQUE(http://cygwin.com/ml/binutils/2011-10/msg00276.html) We need to rebuild the toolchain/ or is there any option at compile time to fix. Kind regards

12 years, 8 months

2
1
0 0

[ACTIVITY] 2-4 Jan 2013

by Renato Golin

== This Week == * Setting up laptop, desk, mailing lists, SSH keys, Launchpad, etc * Livermore Loops Benchmark * It fails on some types of builds but not others * Failure is due to LTO, problem identified, trying to get a reduced case * Getting LLVM building nightly and running the test-suite * Got where we are with ARM and others regarding buildbots * LLVM compiles and checks on pandaboard, need test-suite * Got a Chromebook to run the test-suite * LLVM web presence (pages, svn repositories, etc) dead == Next Week == * Reduce the LTO bug on Livermore kernels * Report it once I have more information and a reduced case * Try to fix it * Checkout Zorg (LLVM's build system integrator) * Force builds to use LNT (new test harness, which passes) * Someone else is looking into setting up consistent LTO tests to the rest already * Get Ubuntu on Chromebook and build LLVM on it + test-suite * Understand the CBuild infrastructure and setup a board to do it automatically * Revise the current LLVM build to be continuous and check-all * Help Nadav Rotem (Apple) with the cost model for vectorization on ARM VFP/NEON * Meeting with ARM and "le French" to finalize the EuroLLVM 2013 and send the CFP == Future == * Validate vectorization for ARM after cost model is reasonably accurate * Vectorization will be turned on by default as of 3.3 on -O2 or higher * Reduced strength with -Os, but still on * Make Livermore Loops vectorize * Allow vectorization to detect global structures as safe * Allow floating point vectorization if using -unsafe-math * Plan a workflow to report / fix bugs that our internal CBuild finds on ARM * Liaise with ARM on what processes can be shared / commoned-up * Try to be less verbose on activity reports...

12 years, 8 months

1
0
0 0

[ACTIVITY] 2-4 January 2013

by Matthew Gretton-Dann

== Blueprints == Initial Current Actual fix-gcc-multiarch-testing 31 Dec 2012 31 Jan 2013 == Progress == * Short week, working Weds-Fri * Admin * Welcomed Renato to the team, and discussions with him about LLVM * Initial project setup for llvm-linaro. * Finished putting current set of card drafts into Jira * Did GCC merges * Backport of Thumb literal pool issues to 4.7. == Next week == * Prepare Cortex Strings release * Ensure GCC backports are up to date. * Merge reviewing week. * Catch up on outstanding cards. == Future == * Run HOT/COLD partitioning benchmarks * Analyse ARM results * On x86_64 to see what the actual benefit we could get * fix-gcc-multiarch-testing * Come up with strawman proposal for updating testsuite to handle testing with varying command-line options. -- Matthew Gretton-Dann Toolchain Working Group, Linaro

12 years, 8 months

1
0
0 0

Recompile linaro-toolchain for windows failured

by ljc

Hi all! I use the arm-linux-gnueabihf-ct-ng.config in gcc-linaro-arm-linux-gnueabihf-4.7-2012.12-20121214_win32.zip to rebuild linaro-toolchain,but failured with the fellow messages: [INFO ] Performing some trivial sanity checks [INFO ] Build started 20130104.110952 [INFO ] Building environment variables [WARN ] Directory '/home/ljc/ct-ng/crosstool-ng-linaro-1.13.1-4.7-2012.12-20121214/mybuild/tarballs' does not exist. [WARN ] Will not save downloaded tarballs to local storage. [EXTRA] Preparing working directories [EXTRA] Installing user-supplied crosstool-NG configuration [EXTRA] ================================================================= [EXTRA] Dumping internal crosstool-NG configuration [EXTRA] Building a toolchain for: [EXTRA] build = i686-pc-linux-gnu [EXTRA] host = i586-mingw32msvc [EXTRA] target = arm-linux-gnueabihf [EXTRA] Dumping internal crosstool-NG configuration: done in 0.26s (at 00:04) ........ [EXTRA] Saving state to restart at step 'binutils'... [INFO ] ================================================================= [INFO ] Installing binutils [EXTRA] Configuring binutils [EXTRA] Building binutils [ERROR] /home/ljc/ct-ng/crosstool-ng-linaro-1.13.1-4.7-2012.12-20121214/mybuild/.build/src/binutils-2.22/gold/arm.cc:2173: internal compiler error: in make_rtl_for_nonlocal_decl, at cp/decl.c:4971 [ERROR] make[5]: *** [arm.o] Error 1 [ERROR] make[4]: *** [all-recursive] Error 1 [ERROR] make[3]: *** [all] Error 2 [ERROR] make[2]: *** [all-gold] Error 2 [ERROR] make[1]: *** [all] Error 2 [ERROR] [ERROR] >> [ERROR] >> Error happened in: main[scripts/crosstool-NG.sh] [ERROR] >> [ERROR] >> For more info on this error, look at the file: 'build.log' [ERROR] >> There is a list of known issues, some with workarounds, in: [ERROR] >> 'share/doc/ct-ng-linaro-1.13.1-4.7-2012.12-20121214/B - Known issues.txt' [ERROR] [ERROR] Build failed in step 'Extracting and patching toolchain components' [ERROR] [ERROR] (elapsed: 57:51.80) make: *** [build] 错误 2 And in build.log: .......... [ALL ] /home/ljc/ct-ng/crosstool-ng-linaro-1.13.1-4.7-2012.12-20121214/mybuild/.build/src/binutils-2.22/gold/arm.cc:11999: instantiated from here [ERROR] /home/ljc/ct-ng/crosstool-ng-linaro-1.13.1-4.7-2012.12-20121214/mybuild/.build/src/binutils-2.22/gold/arm.cc:2173: internal compiler error: in make_rtl_for_nonlocal_decl, at cp/decl.c:4971 [ALL ] Please submit a full bug report, [ALL ] with preprocessed source if appropriate. [ALL ] See <URL:http://www.mingw.org/bugs.shtml> for instructions. [ERROR] make[5]: *** [arm.o] Error 1 [ALL ] make[5]: *** Waiting for unfinished jobs.... [ALL ] mv -f .deps/powerpc.Tpo .deps/powerpc.Po [ALL ] make[5]: Leaving directory `/home/ljc/ct-ng/crosstool-ng-linaro-1.13.1-4.7-2012.12-20121214/mybuild/.build/arm-linux-gnueabihf/build/build-binutils/gold' [ERROR] make[4]: *** [all-recursive] Error 1 [ALL ] make[4]: Leaving directory `/home/ljc/ct-ng/crosstool-ng-linaro-1.13.1-4.7-2012.12-20121214/mybuild/.build/arm-linux-gnueabihf/build/build-binutils/gold' [ERROR] make[3]: *** [all] Error 2 [ALL ] make[3]: Leaving directory `/home/ljc/ct-ng/crosstool-ng-linaro-1.13.1-4.7-2012.12-20121214/mybuild/.build/arm-linux-gnueabihf/build/build-binutils/gold' [ERROR] make[2]: *** [all-gold] Error 2 [ALL ] make[2]: Leaving directory `/home/ljc/ct-ng/crosstool-ng-linaro-1.13.1-4.7-2012.12-20121214/mybuild/.build/arm-linux-gnueabihf/build/build-binutils' [ERROR] make[1]: *** [all] Error 2 [ALL ] make[1]: Leaving directory `/home/ljc/ct-ng/crosstool-ng-linaro-1.13.1-4.7-2012.12-20121214/mybuild/.build/arm-linux-gnueabihf/build/build-binutils' [ERROR] [ERROR] >> [ERROR] >> Error happened in: main[scripts/crosstool-NG.sh] [ERROR] >> [ERROR] >> For more info on this error, look at the file: 'build.log' [ERROR] >> There is a list of known issues, some with workarounds, in: [ERROR] >> 'share/doc/ct-ng-linaro-1.13.1-4.7-2012.12-20121214/B - Known issues.txt' [ERROR] [ERROR] Build failed in step 'Extracting and patching toolchain components' [ERROR] [ERROR] (elapsed: 57:51.80) Has anybody met this problem too?

12 years, 8 months

2
1
0 0

R_ARM_TLS_DTPMOD32 Relocation

by naveen yadav

Dear All, When doing prelink I got following error. /a.out /a.out: R_ARM_TLS_DTPMOD32 reloc in executable? Gcc version 4.6 I have following question: 1. What this relocation do. ? 2. Is it problem in tool chain ? 3. Are we need to fix this in Prelink utils Thanks

12 years, 8 months

2
2
0 0

int64_t definition conflict on Aarch64

by Riku Voipio

Hi, The following code fails to build with OE Aarch64 toolchain with current kernel headers. While ugly, the code is a reduced testcase from fuse build failure ( https://bugs.launchpad.net/linaro-oe/+bug/1087757 ) and the same fuse code compiles on all other architectures. Before I send a workaround for upstream, I'd like to know how we can end up with different definitions for int64_t when that happens on no other architectures - something wrong with the generic kernel headers? Testcase: #include <sys/types.h> #define __s64 int64_t #include <signal.h> int main(int argc, char **argv) { int64_t x=4; return x; } Failure: /data/oe/build/tmp-eglibc/sysroots/x86_64-linux/usr/bin/aarch64-oe-linux/aarch64-oe-linux-gcc -save-temps --sysroot=/data/oe/build/tmp-eglibc/sysroots/genericarmv8 -o test test.c In file included from /data/oe/build/tmp-eglibc/sysroots/genericarmv8/usr/include/asm-generic/types.h:7:0, from /data/oe/build/tmp-eglibc/sysroots/genericarmv8/usr/include/asm/types.h:1, from /data/oe/build/tmp-eglibc/sysroots/genericarmv8/usr/include/linux/types.h:4, from /data/oe/build/tmp-eglibc/sysroots/genericarmv8/usr/include/asm/sigcontext.h:19, from /data/oe/build/tmp-eglibc/sysroots/genericarmv8/usr/include/bits/sigcontext.h:27, from /data/oe/build/tmp-eglibc/sysroots/genericarmv8/usr/include/signal.h:338, from test.c:4: /data/oe/build/tmp-eglibc/sysroots/genericarmv8/usr/include/asm-generic/int-ll64.h:29:44: error: conflicting types for 'int64_t' In file included from test.c:2:0: /data/oe/build/tmp-eglibc/sysroots/genericarmv8/usr/include/sys/types.h:197:13: note: previous declaration of 'int64_t' was here

12 years, 8 months

2
5
0 0

[Activity] Week 52

by Zhenqiang Chen

Summary: * Follow-up shrink-up and branch cost related work. * Investigate "MSR FPEXC, r2" assemble fail issues. Details: 1. RM toolchain related work. 2. Investigate "MSR FPEXC, r2" assemble fail issues. * According to Reference Manual, should use VMSR/VMRS to access FPEXC register other than MSR/MRS. * Binutils 2.23.1 or later had enhanced VMRS/VMSR to accept FPEXC register. 3. Rebase and test the shrink-wrap patches. 4. Read codes about impact of branch-cost. Plan: * Follow up the shrink-wrap and branch cost related work. Planed leaves: * Jan. 1-3, 2013 Best Regards! -Zhenqiang

12 years, 8 months

1
0
0 0

Cant't read arm-linux-gnueabihf-ct-ng.config

by ljc

Hi all! I'm rebuildding linaro-toolchain with ct-ng,I expect use the configure file in linaro-toolchain-binaries ,but I can't read the options in it's arm-linux-gnueabihf-ct-ng.config. How I can do? Thanks!

12 years, 8 months

2
1
0 0

[ACTIVITY] 17-21 December 2012

by Christophe Lyon

== Progress == * 64-bits ops in Neon: re-posted patch after a bit of cleanup requested by upstream. Investigated Fortran regression: confirmed unrelated to this patched, and fixed upstream. * disable-peeling: launched jobs under cbuild to perform initial benchmarking * builtin_bswap16 backport to linaro-4.7: almost OK, missing some pending validation results. * cbuild: investigated some reporting problems which were slowing down the branch review process. == Next == * handle 64-bits bitops in Neon feedback from upstream if any * finish builtin_bswap16 backport * benchmark with vectorizer cost model enabled with its default configuration == Future == Back on January 7th, after the end of the world.

12 years, 8 months

1
0
0 0

[ACTIVITY] 17-21 December 2012

by Matthew Gretton-Dann

== Blueprints == Initial Current Actual initial-aarch64-backport 31 Oct 2012 31 Dec 2012 21 Dec 2012 aarch64-baremetal-testing 31 Oct 2012 31 Dec 2012 21 Dec 2012 backport-fma-intrinsic 31 Dec 2012 Brice fused-multiply-add-support 31 Dec 2012 Brice gcc-investigate-lra-for-arm 31 Dec 2012 Brice fix-gcc-multiarch-testing 31 Dec 2012 31 Jan 2013 == Progress == * Admin * Interviewing * Welcomed Brice Dobry to the working group * Started inputting cards into cards.linaro.org * Discussions about KVM * Discussions about Toolchain/Platform interactions * initial-aarch64-backport and aarch64-baremetal-testing * Finished documentation == Next (working) week == * Admin * Finish loading card drafts into Jira. * Welcome Renato to working group. * Do monthly GCC merges * Prepare Cortex Strings release * Ensure GCC backports are up to date. == Future == * Run HOT/COLD partitioning benchmarks * Analyse ARM results * On x86_64 to see what the actual benefit we could get * fix-gcc-multiarch-testing * Come up with strawman proposal for updating testsuite to handle testing with varying command-line options. -- Matthew Gretton-Dann Linaro Toolchain Working Group matthew.gretton-dann(a)linaro.org

12 years, 8 months

1
0
0 0

Re: [Merge] lp:~brice-dobry/gcc-linaro/fma into lp:gcc-linaro

by Matthew Gretton-Dann

On 21 December 2012 09:54, Yvan Roux <yvan.roux(a)linaro.org> wrote: > Matt, do you have something particular in mind to put in a shared and versioned .bzrignore file ? > My understanding of its usage is that it is more a user side configuration of the archive. > (Maybe we could chat about this topic on another channel) Yes this conversation should probably be conducted elsewhere :-) - moved to linaro-toolchain. If you look at upstream SVN GCC and do svn propget svn:ignore you get a long list of files that SVN is set up to ignore. And whilst there isn't a .gitignore other upstream projects which have git mirrors do put a .gitignore in place (see GDB for instance). I think having a .bzrignore which is a copy of the svn:ignore set up (and the defaults that SVN ignores but aren't on bzr's list) would be valid in the repo. Although as I said in the original thread - let's do this when we branch 4.8 and not to the historic branches. Thanks, Matt -- Matthew Gretton-Dann Linaro Toolchain Working Group matthew.gretton-dann(a)linaro.org

12 years, 8 months

1
0
0 0

[ANNOUNCE] Linaro Toolchain Binaries 2012.12 released

by Zhenqiang Chen

The Linaro Toolchain Working Group is pleased to announce the 2012.12 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 2012.12 * 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. 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/2012.12 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, 9 months

1
0
0 0

[ACTIVITY] 10 - 14 December 2012

by Yvan Roux

== Progress == * Release week: - Made 2012.12 release of gcc-linaro 4.6 and 4.7. - took lot of time (infrastructure, right acess, Lava lab migration) * GCC atomic builtins: - my load acquire patch was applied up-stream (trunk and 4.7). - some cleaning in optabs.c (patch applied up-stream too). == Next == * Resume Boehm GC AArch64 support. * Review roster.

12 years, 9 months

1
0
0 0

[ACTIVITY] 10 - 14 December 2012

by Christophe Lyon

== Progress == * gdb-linaro-7.5-2012.12 release - Updated wikis about gdb sources import from upstream and about gdb-linaro release - still some trouble with infrastructure to achieve the release * 64-bits ops in Neon: no news from upstream * disable-peeling: upstream advice is to enable & tune the vectorizer cost model first, but there seems to be an agreement that if unaligned accesses have no penalty, peeling should not be considered. Updated the vectorizer-cost-model blueprint * builtin_bswap16 backport to linaro-4.7: the i686 regression was caused by the build process. Re-spawned the jobs after fixing the remaining arm issue * cbuild: briefly looked at some scripts to better understand the whole system, while tracking a problem in the gdb validation reports == Next == * handle 64-bits bitops in Neon and disable-peeling feedback from upstream if any * finish builtin_bswap16 backport == Future == * on holidays for 2 weeks (Dec 22th-Jan 6th)

12 years, 9 months

1
0
0 0

[ACTIVITY] 10 - 14 December

by Matthew Gretton-Dann

== Blueprints == Initial Current Actual initial-aarch64-backport 31 Oct 2012 31 Dec 2012 aarch64-baremetal-testing 31 Oct 2012 31 Dec 2012 backport-fma-intrinsic 31 Dec 2012 Brice fused-multiply-add-support 31 Dec 2012 Brice gcc-investigate-lra-for-arm 31 Dec 2012 31 Dec 2012 fix-gcc-multiarch-testing 31 Dec 2012 31 Jan 2013 == Progress == * Admin * Interviewing * Took over from Michael * New Starter prep * Updated card drafts * Discussions about LEG/TCWG interactions * Discussions about KVM * Discussions about Toolchain/Platform interactions == Next Week == * Upload card drafts into Jira. * initial-aarch64-backport and aarch64-baremetal-testing * Complete documentation == Future == * gcc-investigate-lra-for-arm * Analyse benchmarks * Run HOT/COLD partitioning benchmarks * Analyse ARM results * On x86_64 to see what the actual benefit we could get * fix-gcc-multiarch-testing * Come up with strawman proposal for updating testsuite to handle testing with varying command-line options. -- Matthew Gretton-Dann Linaro Toolchain Working Group matthew.gretton-dann(a)linaro.org

12 years, 9 months

1
0
0 0

[ACTIVITY] report week 50

by Peter Maydell

* qemu-linaro 2012.12 release * arm-devs pullreq sent * wrote a patch for some minor TCG leaks * more virtio patch review * various other upstream arm devs review * discussion re KVM planning, etc * usual collection of meetings and calls KVM blueprint progress tracker (note new url): http://cbuild.validation.linaro.org/helpers/backlog?group_by=topic&colour_b… -- PMM

12 years, 9 months

1
0
0 0

Clearing out past branches

by Michael Hope

Hi Ramana. You have the following branches remaining on Launchpad: * lp:~ramana/gcc-linaro/47-lower-subreg-experiments * lp:~ramana/gcc-linaro/47-improve-neon-intrinsics * lp:~ramana/gcc-linaro/47-nobble-promote-mode * lp:~ramana/gcc-linaro/47-smin-umin-idiom Which are obsolete, which should be spun out into backlog blueprints, and which should be taken over by someone? -- Michael

12 years, 9 months

2
3
0 0

[Activity] Week 50

by Zhenqiang Chen

Summary: * Validate RM toolchain * Prepare Linaro Toolchain Binaries 2012.12 release. * Collect performance data for different branch cost. Details: 1. Validate RM toolchain release. 2. Collect denbench and spec2000int performance data for branch cost tuning. 3. Fix README issue (lp:1068402) by dynamically create README.txt: * The hard coded README.txt is removed. * Update build scripts to generate the README.txt, which depends on - README.texi, which is the common template for all TARGETS. - config.texi, which sets the default configuration for the TARGET. Each TARGET has a config.texi. - version.texi, created during build, includes GCC_VERSION, GDB_VERSION and TOOLCHAIN_VERSION. 4. Update Linaro GCC and GDB to 2012.12 in Linaro crosstool-ng, workaround gdb mingw32 link fail issue (due to mbsrtowcs is redefined in gdb/gnulib), finish the smoke test and spawn release builds. Plans: * Investigate how branch cost impacts on code generation. * Release Linaro Toolchain Binaries 2012.12. Best regards! -Zhenqiang

12 years, 9 months

1
0
0 0

[ANNOUNCE] Linaro GCC 4.7 and 4.6 2012.12 released

by Yvan Roux

The Linaro Toolchain Working Group is pleased to announce the 2012.12 release of both Linaro GCC 4.7 and Linaro GCC 4.6. Linaro GCC 4.7 2012.12 is the ninth release in the 4.7 series. Based off the latest GCC 4.7.2+svn194184 release, it includes ARM-focused performance improvements and bug fixes. Interesting changes include: * Updates to GCC 4.7.2+svn19184 * Better 64 bit shifts in NEON * Also includes arm/aarch64-4.7-branch up to svn revision 194154. Fixes: * LP #1060221 Linaro GCC 4.6 2012.12 is the 22st release in the 4.6 series. Based off the latest GCC 4.6.3+svn194340 release, this is the ninth release after entering maintenance. Interesting changes include: * Updates to 4.6.3+svn194340 The source tarballs are available from: https://launchpad.net/gcc-linaro/+milestone/4.7-2012.12 https://launchpad.net/gcc-linaro/+milestone/4.6-2012.12 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-2012.12 https://launchpad.net/gcc-linaro/4.6/4.6-2012.12 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 -- Yvan Roux Linaro Toolchain Working Group yvan.roux(a)linaro.org

12 years, 9 months

1
0
0 0

[ANNOUNCE] Linaro GDB 7.5 2012.12 released

by Christophe Lyon

The Linaro Toolchain Working Group is pleased to announce the release of Linaro GDB 7.5. Linaro GDB 7.5 2012.12 is the second release in the 7.5 series. ***NOTE*** Linaro GDB 7.5 2012.12 is identical to the FSF GDB 7.5.1 release, except for the change in version number and Linaro branding, since all Linaro GDB features were already accepted upstream and are included in the FSF release as-is. Future releases in the Linaro GDB 7.5 series may include additional ARM-focused bug fixes and enhancements. The source tarball is available at: https://launchpad.net/gdb-linaro/+milestone/7.5-2012.12 More information on Linaro GDB is available at: https://launchpad.net/gdb-linaro Christophe Lyon

12 years, 9 months

1
0
0 0

[ANNOUNCE] Linaro QEMU 2012.12 released

by Peter Maydell

The Linaro Toolchain Working Group is pleased to announce the release of Linaro QEMU 2012.12. Linaro QEMU 2012.12 is the latest release of qemu-linaro. Based off upstream (trunk) QEMU, it includes a number of ARM-focused bug fixes and enhancements. There are no major changes in this month's release, but it has been updated to be based on upstream's recent 1.3.0 release. The source tarball is available at: https://launchpad.net/qemu-linaro/+milestone/2012.12 More information on Linaro QEMU is available at: https://launchpad.net/qemu-linaro -- PMM

12 years, 9 months

1
0
0 0

[PATCH] Cortex Strings AArch64 implementations of memcpy, memset, strcmp

by Marcus Shawcroft

This patch adds aarch64 implementations of memcpy, memset and strcmp to cortex strings. /Marcus

12 years, 9 months

2
2
0 0

FPU error with arm-linux-gnueabihf-gcc 3.7.3

by Zhangfei Gao

We met build error when using arm-linux-gnueabihf-gcc 3.7.3 for Huawei s40v200 kernel, which is 3.0.8, log is below. HAVE issue: gcc-linaro-arm-linux-gnueabihf-4.7-2012.11-20121123_linux.tar.bz2 gcc-linaro-arm-linux-gnueabihf-4.7-2012.10-20121022_linux.tar.bz2 gcc-linaro-arm-linux-gnueabi-2012.03-20120326_linux.tar.bz2, with build flag *--with-float=softfp* NO issue: arm-eabi-gcc 4.4.0, which comes from android package. Any suggestion? Thanks make[1]: `include/generated/mach-types.h' is up to date. CALL scripts/checksyscalls.sh CHK include/generated/compile.h AS arch/arm/mach-godbox/hi_pm_sleep.o arch/arm/mach-godbox/hi_pm_sleep.S: Assembler messages: arch/arm/mach-godbox/hi_pm_sleep.S:456: Error: selected processor does not support requested special purpose register -- `mrs r10,FPEXC' arch/arm/mach-godbox/hi_pm_sleep.S:456: Error: selected processor does not support requested special purpose register -- `msr FPEXC,r2' arch/arm/mach-godbox/hi_pm_sleep.S:456: Error: selected processor does not support requested special purpose register -- `mrs r2,FPSCR' arch/arm/mach-godbox/hi_pm_sleep.S:546: Error: selected processor does not support requested special purpose register -- `msr FPEXC,r2' arch/arm/mach-godbox/hi_pm_sleep.S:546: Error: selected processor does not support requested special purpose register -- `msr FPSCR,r10' arch/arm/mach-godbox/hi_pm_sleep.S:546: Error: selected processor does not support requested special purpose register -- `msr FPEXC,r9' make[1]: *** [arch/arm/mach-godbox/hi_pm_sleep.o] Error 1 make: *** [arch/arm/mach-godbox] Error 2 make: *** Waiting for unfinished jobs....

12 years, 9 months

3
2
0 0

[PATCH] Cortex Strings and configury for AArch64

by Marcus Shawcroft

Following this mornings set of patches, this patch adds configury for aarch64 support. /Marcus

12 years, 9 months

2
1
0 0

[PATCH 5/5] cortex strings preparation for aarch64

by Marcus Shawcroft

This patch adds --std=gnu99 to CFLAGS for the tests. This is necessary because some of the test code use the following c99 idiom: for (int x=....) /Marcus

12 years, 9 months

2
1
0 0

[PATCH 4/5] cortex strings preparation for aarch64

by Marcus Shawcroft

Adding definitions for LDADD and CFLAGS when building strchr and memchr tests. /Marcus

12 years, 9 months

2
1
0 0

[PATCH 2/5] cortex strings preparation for aarch64

by Marcus Shawcroft

This patch adds support for --host=TRIPLE to configure which is convenient for cross building. /Marcus

12 years, 9 months

2
1
0 0

[PATCH 1/5] cortex strings preparation for aarch64

by Marcus Shawcroft

This patch is just a minor whitespace cleanup. /Marcus

12 years, 9 months

2
1
0 0

[MINUTES] Toolchain main Call 2012-12-10

by Michael Hope

The minutes of the main call held on 10 December 2012 can be found at: https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2012-12-10 In summary the actions from the meeting are: * ACTION: Yvan to post mail to linaro-toolchain(a)lists.linaro.org re: 4.6 armv5 sync failures * ACTION: Matt review 4.7 AArch64 merge * ACTION: Michael to check that the GDB snapshots claiming to be 7.7 are actually 7.6 * ACTION: everyone update the Linaro Leaves calendar for Christmas * ACTION: Matt to look inside ARM re: EEMBC Office gs8 failures * ACTION: Matt will send Ilias the KVM person names * ACTION: re: left over branches: Michael to send an email and Ramana follow up Thanks, -- Michael

12 years, 9 months

1
0
0 0

regression of x86 gcc bootstrap with Linaro sourcebase

by Robert Schiele

Hi Ulrich, Before I build the cross compiler for ARM target I do a bootstrap process of an i686 compiler on the same code base to use that one building the cross compiler to reduce the chance of seeing subtle problems late in the game. This process unveiled a x86 bootstrap regression with some of your changes on the Linaro 4.7 branch. It all boils down to the following set of changes you did: commit c904094f2421bbd5d2cab6d7fbccecf055509629 Author: Ulrich Weigand <uweigand(a)de.ibm.com> Date: Mon Jul 16 16:31:58 2012 +0200 Update to exactly reflect upstream version. commit bf378903a1b749b904ae64635182e7fc9b43e0e4 Author: Ulrich Weigand <uweigand(a)de.ibm.com> Date: Tue Jul 10 15:46:51 2012 +0200 Fix backport. commit e0c3b0a21916ffafc058cd88d82423d87ce77b50 Author: Ulrich Weigand <uweigand(a)de.ibm.com> Date: Mon Jul 9 22:52:10 2012 +0200 Fix LP 1020601. This is the introduction of optimize_unreachable in gcc/tree-ssa-ccp.c. When configuring with ../gcc/configure --host=i686-build_pc-linux-gnu --build=i686-build_pc-linux-gnu --target=i686-build_pc-linux-gnu --prefix=/ --libexecdir=//lib --program-prefix=i686-build_pc-linux-gnu- --with-sysroot=/user/rschiele/l/builddir/i686-build_pc-linux-gnu/sysroot --with-local-prefix=/user/rschiele/l/builddir/i686-build_pc-linux-gnu/sysroot --with-gmp=/user/rschiele/l/builddir/i686-build_pc-linux-gnu/sysroot/usr --with-mpfr=/user/rschiele/l/builddir/i686-build_pc-linux-gnu/sysroot/usr --with-mpc=/user/rschiele/l/builddir/i686-build_pc-linux-gnu/sysroot/usr --with-cloog=/user/rschiele/l/builddir/i686-build_pc-linux-gnu/sysroot/usr --with-ppl=/user/rschiele/l/builddir/i686-build_pc-linux-gnu/sysroot/usr '--with-host-libstdcxx=/user/rschiele/l/builddir/i686-build_pc-linux-gnu/tools/lib/libstdc++.a -lm' --disable-multilib --disable-checking --enable-__cxa_atexit --enable-libmudflap --enable-libgomp --enable-libssp --enable-languages=c,c++ --enable-threads=posix --disable-libstdcxx-pch --enable-c99 --enable-long-long --disable-shared It fails in the bootstrap at /user/rschiele/l/src/gccbuild/./prev-gcc/g++ -B/user/rschiele/l/src/gccbuild/./prev-gcc/ -B//i686-build_pc-linux-gnu/bin/ -nostdinc++ -B/user/rschiele/l/src/gccbuild/prev-i686-build_pc-linux-gnu/libstdc++-v3/src/.libs -B/user/rschiele/l/src/gccbuild/prev-i686-build_pc-linux-gnu/libstdc++-v3/libsupc++/.libs -I/user/rschiele/l/src/gccbuild/prev-i686-build_pc-linux-gnu/libstdc++-v3/include/i686-build_pc-linux-gnu -I/user/rschiele/l/src/gccbuild/prev-i686-build_pc-linux-gnu/libstdc++-v3/include -I/user/rschiele/l/src/gcc/libstdc++-v3/libsupc++ -L/user/rschiele/l/src/gccbuild/prev-i686-build_pc-linux-gnu/libstdc++-v3/src/.libs -L/user/rschiele/l/src/gccbuild/prev-i686-build_pc-linux-gnu/libstdc++-v3/libsupc++/.libs -c -g -O2 -gtoggle -DIN_GCC -fno-exceptions -fno-rtti -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/../include -I../../gcc/gcc/../libcpp/include -I/user/rschiele/l/builddir/i686-build_pc-linux-gnu/sysroot/usr/include -I/user/rschiele/l/builddir/i686-build_pc-linux-gnu/sysroot/usr/include -I/user/rschiele/l/builddir/i686-build_pc-linux-gnu/sysroot/usr/include -I../../gcc/gcc/../libdecnumber -I../../gcc/gcc/../libdecnumber/bid -I../libdecnumber -I/user/rschiele/l/builddir/i686-build_pc-linux-gnu/sysroot/usr/include -I/user/rschiele/l/builddir/i686-build_pc-linux-gnu/sysroot/usr/include ../../gcc/gcc/sel-sched.c -o sel-sched.o ../../gcc/gcc/sel-sched.c: In function 'void sel_sched_region_2(int)': ../../gcc/gcc/sel-sched.c:7472:1: error: mismatching comparison operand types struct rtx_def * bool if (insn_1716 == 0) ../../gcc/gcc/sel-sched.c:7472:1: internal compiler error: verify_gimple failed Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. Note, that the --disable-checking is essential to reproduce. As soon as you do --enable-checking the bootstrap completes successfully. I would assume that you then still have the bug in the compiler but it is just subtle enough not to be triggered then. Reverting your mentioned changes fixes this problem. If you need further information about my environment to reproduce the problem feel free to contact me. Greetings, Robert

12 years, 9 months

2
2
0 0

[MINUTES] Toolchain Performace Call 2012-12-11

by Yvan Roux

The minutes of the performance call held on 11 December 2012 can be found at: https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2012-12-11 In summary the actions from the meeting are: * ACTION: Matt update meeting template attendees - to include Yvan * ACTION: mgrettondann split LRA blueprint * ACTION: Christophe to update Hot/Cold partitioning bugzilla * ACTION: mgrettondann: benchmark on Hold/Cold partitioning * ACTION: Christophe to look at the loop peeling cost Thanks, Yvan

12 years, 9 months

1
0
0 0

[PATCH 3/5] cortex strings preparation for aarch64

by Marcus Shawcroft

This patch provides support to detect the host architecture in configure.in use the detected architecture to conditionalize parts of the Makefile.am. The intention is that we retain a single top level Makefile which contains rules relevant to all supported architectures, each gated by the AM_CONDITIONAL infrastructure. /Marcus

12 years, 9 months

1
0
0 0

[PATCH 0/5] cortex strings preparation for aarch64

by Marcus Shawcroft

Folks, In preparation for adding aarch64 string functions into cortex-strings, I'd like feed back on the following series of patches. 1/5 Trivial whitespace cleanups. 2/5 Autotools foo for cross building support. 3/5 Autotools foo for architecture detection. 4/5 Missing LDADD and CFLAGS setting. 5/5 Use --std=gnu99 I'm particularly interested in views on 3/5. This patch sets direction for autoconf detection of the host architecture. The intention is that we retain the single toplevel Makefile.am which gains AM_CONDITIONAL support for the detected host triple. The aarch64 specific code will follow in a different patch set. Cheers /Marcus

12 years, 9 months

1
0
0 0

4.6 merge: ARMv5 sync_synchronize failures

by Yvan Roux

Hi, the issue seems indeed to be introduced by r193959 and fixed in r194161, as it is reported in: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55571 Unfortunately, my merge attempt was at r190461 :( I redo the merge... Yvan

12 years, 9 months

1
0
0 0

[ACTIVITY] 3-7 December 2012

by Yvan Roux

== Progress == * 4.6 and 4.7 merges - Many merge attempts - 4.7 merged - 4.6 under approval * Boehm GC AArch64 support: - Resume the libatomic work - started the garbage collector configuration * Internal support. == Next == * Do GCC-linaro releases * Boehm GC

12 years, 9 months

1
0
0 0

[ACTIVITY] week 49

by Mans Rullgard

* https://blueprints.launchpad.net/linaro-toolchain-misc/+spec/webp-upsamplin… - working 'fancy' upsampling, actual yuv-rgb conversion still major time hog - next: do yuv-rgb conversion in neon * reported valgrind bug https://bugs.kde.org/show_bug.cgi?id=311318 * implemented runtime cpu feature (neon, vfp, etc) detection in Libav * ongoing: tracking gcc trunk on Libav test systems, no ARM regressions this week * user support on irc -- Mans Rullgard / mru

12 years, 9 months

1
0
0 0

[Activity] Week 49

by Zhenqiang Chen

Summary: * Validate RM toolchain, Linaro QENU 2012.12 and Linaro aarch64 2012.11. * Collect performance data for different branch cost. Details: * Validate RM toolchain release. * Set up test environment with the help of Michael and validate Linaro QEMU 2012.12 release. * Validate aarch64 toolchain 2012.11. From 2012.12, it will be released regularly like arm-linux-gnueabihf toolchain. * Collect denbench and spec2000int performance data for branch cost tuning. * Investigate how to do copy propagation for shrink-wrap to optimize 453.povray benchmark. Will reuse current codes in pass_cprop_hardreg. Plans: * Performance reports for branch cost tuning. * Fix README issue (lp:1068402) in Linaro crosstool-ng. Best regards! -Zhenqiang

12 years, 9 months

1
0
0 0

What tools can be used to protect the KVM and qemu quality？

by chenq

Hi all， I am a rookie, and now I'm focusing on ARM virtualization. As we know,KVM (for Kernel-based Virtual Machine) is a full virtualization solution. KVM-Autotest is a set of virtualization tests for X86 platform, but it may not be suitable for ARM.I want to know, in the linaro , what tools can protect the KVM and qemu quality ? Thanks and Regards,Qun Chen

12 years, 9 months

2
1
0 0

[ACTIVITY] report week 49

by Peter Maydell

* usual set of meetings etc * rebased qemu-linaro on upstream 1.3, rolled tarball for 2012.12; Zhenqiang has tested it and it should be ready to go next week * qemu arm patch catchup; pinging or resending some patches of mine from before upstream freeze * applied a set of boot-wrapper patches from tixy * virtio patch code review: design definitely coming together now KVM blueprint progress tracker (note new url): http://cbuild.validation.linaro.org/helpers/backlog?group_by=topic&colour_b… -- PMM

12 years, 9 months

1
0
0 0

[ACTIVITY] 3-7 December 2012

by Christophe Lyon

== Progress == * Turn off 64-bits bitos in Neon: Ping-ed patch proposal. * Disable peeling: benchmarks show good results; sent a proposal upstream to discuss preliminary implementation & needed testsuite modifications. * builtin_bswap16 backport to linaro-4.7: need to investigation an unexpected regression reported for i686 target. * Updated gdb linaro sources to 7.5.1, exercising the release process. * Trying to bootstrap gcc-linaro/4.7 on board: need to retry with a different rootfs distribution. == Next == * handle 64-bits bitops in Neon and disable-peeling feedback from upstream if any. * finish builtin_bswap16 backport

12 years, 9 months

1
0
0 0

[ACTIVITY] 3-7 December 2012

by Matthew Gretton-Dann

== Blueprints == Initial Current Actual initial-aarch64-backport 31 Oct 2012 14 Dec 2012 aarch64-baremetal-testing 31 Oct 2012 14 Dec 2012 fix-gcc-multiarch-testing 31 Dec 2012 31 Dec 2012 backport-fma-intrinsic 31 Dec 2012 31 Dec 2012 fused-multiply-add-support 31 Dec 2012 31 Dec 2012 gcc-investigate-lra-for-arm 31 Dec 2012 31 Dec 2012 == Progress == * Admin * Interviewing * Took over from Michael * Preparation for taking over from Michael * re-PINGed triplet backport patches upstream * Patch review * Initial thoughts about cards == Next Week == * initial-aarch64-backport and aarch64-baremetal-testing * Complete documentation * gcc-investigate-lra-for-arm * Analyse benchmarks * Run HOT/COLD partitioning benchmarks * Analyse ARM results * On x86_64 to see what the actual benefit we could get * fix-gcc-multiarch-testing * Come up with strawman proposal for updating testsuite to handle testing with varying command-line options. == Future == * backport-fma-intrinsic & fused-multiply-add-support * Backport patches once fix-gcc-multiarch-testing has been done. -- Matthew Gretton-Dann Linaro Toolchain Working Group matthew.gretton-dann(a)linaro.org

12 years, 9 months

1
0
0 0

selected processor does not support Thumb mode `smc 0'

by Shivamurthy Shastri

Hi, I am trying to compile UEFI code with linaro toolchain version: # arm-linux-gnueabi-gcc --version arm-linux-gnueabi-gcc (Ubuntu/Linaro 4.7.1-5ubuntu1~ppa1) 4.7.1 Copyright (C) 2012 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. I got the erros as follows: "/usr/bin/arm-linux-gnueabi-gcc" -mthumb -march=armv7-a -I/home/shiva/workspace/arndale/edk2/SamsungPlatformPkg/ExynosPkg/Exynos5250/Include/Platform -g -Os -fshort-wchar -fno-strict-aliasing -Wall -Werror -Wno-missing-braces -Wno-array-bounds -c -include AutoGen.h -mword-relocations -mlittle-endian -mabi=aapcs -mapcs -fno-short-enums -save-temps -fsigned-char -ffunction-sections -fdata-sections -fomit-frame-pointer -Wno-address -O0 -o /home/shiva/workspace/arndale/edk2/Build/Arndale-Exynos/DEBUG_ARMLINUXGCC/ARM/SamsungPlatformPkg/ExynosPkg/Exynos5250/Sec/Sec/OUTPUT/./Smc.obj -I/home/shiva/workspace/arndale/edk2/SamsungPlatformPkg/ExynosPkg/Exynos5250/Sec -I/home/shiva/workspace/arndale/edk2/Build/Arndale-Exynos/DEBUG_ARMLINUXGCC/ARM/SamsungPlatformPkg/ExynosPkg/Exynos5250/Sec/Sec/DEBUG -I/home/shiva/workspace/arndale/edk2/MdePkg -I/home/shiva/workspace/arndale/edk2/MdePkg/Include -I/home/shiva/workspace/arndale/edk2/MdePkg/Include/Arm -I/home/shiva/workspace/arndale/edk2/MdeModulePkg -I/home/shiva/workspace/arndale/edk2/MdeModulePkg/Include -I/home/shiva/workspace/arndale/edk2/ArmPkg -I/home/shiva/workspace/arndale/edk2/ArmPkg/Include -I/home/shiva/workspace/arndale/edk2/ArmPlatformPkg -I/home/shiva/workspace/arndale/edk2/ArmPlatformPkg/Include -I/home/shiva/workspace/arndale/edk2/SamsungPlatformPkg/ExynosPkg/Exynos5250 -I/home/shiva/workspace/arndale/edk2/SamsungPlatformPkg/ExynosPkg/Exynos5250/Include /home/shiva/workspace/arndale/edk2/SamsungPlatformPkg/ExynosPkg/Exynos5250/Sec/Smc.c Smc.s: Assembler messages: Smc.s:51: Error: selected processor does not support Thumb mode `smc 0' Is there any issue with the toolchain or any flags I am using? -- Thanks and Regards, Shiva.

12 years, 9 months

2
1
0 0

Scheduler tweaks

by Michael Hope

I've done a couple of tweaks to the scheduler. You now see pending jobs by the class of machine they'll run on. Clicking a job takes you to the detail, which includes a link to drop/cancel the job. -- Michael

12 years, 9 months

1
0
0 0

Toolchain Working Group Meeting Times

by Matthew Gretton-Dann

All, As I mentioned on Monday, due to new members of the team coming on board I am going to rejig the meeting times from 18th December. My proposal is as follows (all times UK Local - UTC+0h winter, UTC+1h summer): 0. These changes will come into effect the week commencing 18th December. 1. The weekly call will happen on a Monday, at 0930 and 1600. You only need to make it to one instance of the call. For those who are physically near each other arranging it so that both calls get attended would be good and notes shared would be good. 2. The Stand-up call will happen on a Thursday, alternating between 0930 and 1600. This is 'best effort' - but please try to attend at least every other week. 3. The performance call will go weekly, and will happen on a Thursday, alternating between 0930 and 1600. If you are on the invite list to this call again please try to attend at least every other week, but if you can manage every week that would be great. If you have any comments on these please can you raise them by the end of the week as I would like to confirm what we are going to do at the call on Monday (at the normal time of 0915UTC). Thanks, Matt -- Matthew Gretton-Dann Linaro Toolchain Working Group matthew.gretton-dann(a)linaro.org

12 years, 9 months

1
0
0 0

[MINUTES] Toolchain Performace Call 2012-12-03

by Michael Hope

The minutes of the performance call held on 3 December 2012 can be found at: https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2012-12-03 In summary the actions from the meeting are: * ACTION: Yvan will do the trunk merge this week * ACTION: Yvan to do the GCC release next week * ACTION: Christophe to do the GDB release branch merge * ACTION: Matt volunteered Zhenqiang as the QEMU manual tester this month * ACTION: Matt: want shrinkwrap to go upstream * ACTION: Matt - Can blueprint improvements in shrink wrap past that * ACTION: Matt to create a blueprint on aarch32 ARMv8 instructions in QEMU * ACTION: Matt to decide if aarch32 ARMv8 instructions in QEMU needs a card * ACTION: Christophe to send Michael cross build failures to investigate Thanks, -- Michael

12 years, 9 months

1
0
0 0

[ACTIVITY] 26-30 November

by Christophe Lyon

== Progress == * Turn off 64-bits bitops in Neon: patch proposed upstream after positive benchmarking. Re-submitted after request to add testcases and documentation for the new option. * Disable peeling: running benchmarks with peeling completely disabled to see the impact. * PGO/hot-cold partitioning: tested new patch from google, which solves some of the ICEs, but makes new ones appear. * builtin_bswap16 backport to Linaro-4.7: checking if there would be a possibility to keep the testcase which fails in one of our configurations, after rebasing my branch. * Trying to bootstrap gcc-linaro/4.7 on board * Internal support == Next == * Follow-up on 64-bits bitops in Neon * Look at benchmarks results with peeling disabled * finish builtin_bswap16 backport

12 years, 9 months

1
0
0 0

random corruption while doing popen pclose

by Ajeet Yadav

Linux version 3.0.33 (Cortex A15) Below program crashes with 2.14.1 glibc but runs fine with 2.11.1 glibc. #include <pthread.h> #include <stdio.h> #include <stdlib.h> #include <signal.h> #include <string.h> #include <errno.h> #define MAX_LINE_SIZE 80 #define MAX_THREAD 20 #define MAX_POPEN 10 #define MALLOC_SIZE 16 void* pipe_thread(void *arg) { int i; char *p = NULL; FILE *fp[MAX_POPEN]; char shellCommand[MAX_LINE_SIZE]; memset(shellCommand, 0x00, MAX_LINE_SIZE); sprintf(shellCommand, "mount"); signal(SIGPIPE, SIG_IGN); while (1) { for (i = 0; i < MAX_POPEN; ++i) { fp[i] = popen(shellCommand, "r"); } if (p) { free(p); } for (i = 0; i < MAX_POPEN; ++i) { if (fp[i]) pclose(fp[i]); } p = malloc(MALLOC_SIZE); if (p) memset(p, 0, MALLOC_SIZE); } return NULL; } int main(int argc, char *argv[]) { int i; pthread_t tid; for (i = 0; i < MAX_THREAD; ++i) { pthread_create(&tid, NULL, &pipe_thread, (void*)NULL); } sleep(60); } gdb logs: (gdb) bt #0 0x4014f998 in _IO_new_fclose (fp=0x1) at iofclose.c:74 #1 0x4015b59c in fwide (fp=0xb8, mode=<optimized out>) at fwide.c:47 #2 0x00008a6c in ?? () Cannot access memory at address 0x8 #3 0x00008a6c in ?? () Cannot access memory at address 0x8 Backtrace stopped: previous frame identical to this frame (corrupt stack?)

12 years, 9 months

1
1
0 0

[Activity] Week 48

by Zhenqiang Chen

Summary: * Verify shrink-wrap related bugs. * Validate and release Linaro toolchain binary 2012.11 release. * Collect performance data for different branch costs. Details: * Validate and release Linaro toolchain binary 2012.11. * Test aarch64 toolchain. All the basic tests PASS except gdbserver. * Collect performance data for branch cost combination. For eembcv1, some combinations have more than 2% performance improvement on PandaBoard THUMB mode. More test results will come later. * Verify shrink-wrap related bugs (http://goo.gl/6fGg5). All pass with the new patch. Native tests are ongoing. Identify the root cause why the copy, which blocks the shrink-wrap optimization for 453.povray benchmark, is not optimized. Plans: * Finalize the aarch64 toolchain binary release plan. * Collect performance data for branch cost tuning. * Enhance shrink-wrap to optimize the copy. Best regards! -Zhenqiang

12 years, 9 months

1
0
0 0

[ACTIVITY] 26-30 November

by Yvan Roux

== Progress == * Boehm GC AArch64 support: - Read wikis and papers on the memory model - Reported an issue with the current ARMv7 atomic builtins - Submitted the fix, which was approved - Improving libatomic-ops AArch64 support with load-acquire/ store-release usage. == Next == * Continue on the Boehm GC AArch64 support.

12 years, 9 months

1
0
0 0

corruption while doing open close

by Ajeet Yadav

Linux version 3.0.33 (Cortex A15) Below program crashes with 2.14.1 glibc but runs fine with 2.11.1 glibc. #include <pthread.h> #include <stdio.h> #include <stdlib.h> #include <signal.h> #include <string.h> #include <errno.h> #define MAX_LINE_SIZE 80 #define MAX_THREAD 20 #define MAX_POPEN 10 #define MALLOC_SIZE 16 void* pipe_thread(void *arg) { int i; char *p = NULL; FILE *fp[MAX_POPEN]; char shellCommand[MAX_LINE_SIZE]; memset(shellCommand, 0x00, MAX_LINE_SIZE); sprintf(shellCommand, "mount"); signal(SIGPIPE, SIG_IGN); while (1) { for (i = 0; i < MAX_POPEN; ++i) { fp[i] = popen(shellCommand, "r"); } if (p) { free(p); } for (i = 0; i < MAX_POPEN; ++i) { if (fp[i]) pclose(fp[i]); } p = malloc(MALLOC_SIZE); if (p) memset(p, 0, MALLOC_SIZE); } return NULL; } int main(int argc, char *argv[]) { int i; pthread_t tid; for (i = 0; i < MAX_THREAD; ++i) { pthread_create(&tid, NULL, &pipe_thread, (void*)NULL); } sleep(60); } gdb logs: (gdb) bt #0 0x4014f998 in _IO_new_fclose (fp=0x1) at iofclose.c:74 #1 0x4015b59c in fwide (fp=0xb8, mode=<optimized out>) at fwide.c:47 #2 0x00008a6c in ?? () Cannot access memory at address 0x8 #3 0x00008a6c in ?? () Cannot access memory at address 0x8 Backtrace stopped: previous frame identical to this frame (corrupt stack?)

12 years, 9 months

2
2
0 0

[ACTIVITY] report week 48

by Peter Maydell

[Short week: 3 days] * looked at (but failed to reproduce) a hang in QEMU reported by Christoffer when shutting down a KVM ARM guest using TUN/TAP networking * investigated LP:1084148 (segfault in qemu usermode) sufficiently to diagnose it as probably another of qemu's "can't handle multithreaded guest programs" bugs * fixed some problems with QEMU's secondary CPU boot code which were masked by errors in QEMU's GIC model but revealed by real hardware (ie KVM); fixed the GIC model bugs as well * investigated LP:955379 (cmake hangs under qemu-arm-static). Tracked down to a race condition involving signal delivery, the fix to which would require the significant redesign I sketched out here a year or so ago: http://lists.gnu.org/archive/html/qemu-devel/2011-12/msg00384.html KVM blueprint progress tracker: http://ex.seabright.co.nz/helpers/backlog?group_by=topic&colour_by=state&pr… -- PMM

12 years, 9 months

1
0
0 0

[ACTIVITY] 26-30 November

by Matthew Gretton-Dann

== Blueprints == Initial Current Actual initial-aarch64-backport 31 Oct 2012 7 Dec 2012* aarch64-baremetal-testing 31 Oct 2012 7 Dec 2012* fix-gcc-multiarch-testing 31 Dec 2012 31 Dec 2012 backport-fma-intrinsic 31 Dec 2012 31 Dec 2012 fused-multiply-add-support 31 Dec 2012 31 Dec 2012 gcc-investigate-lra-for-arm 31 Dec 2012 31 Dec 2012 == Progress == * Admin * Interviewing * Preparation for taking over from Michael * Investigate patches for literal pool layout bug * Applied * PINGed triplet backport patches upstream * Other bug issues * Including an issue running SPEC2K on x86 with recent trunk * And a 4.6 gcc-linaro only issue == Next Week == * Start leading Toolchain team * Run HOT/COLD partitioning benchmarks * Analyse ARM results * On x86_64 to see what the actual benefit we could get * initial-aarch64-backport & aarch64-baremetal-testing * Finish documentation * gcc-investigate-lra-for-arm * Analyse benchmarks * fix-gcc-multiarch-testing * Come up with strawman proposal for updating testsuite to handle testing with varying command-line options. == Future == * backport-fma-intrinsic & fused-multiply-add-support * Backport patches once fix-gcc-multiarch-testing has been done. == Planned Leave == * Monday 24 December - Monday 31 December -- Matthew Gretton-Dann Linaro Toolchain Working Group matthew.gretton-dann(a)linaro.org

12 years, 9 months

1
0
0 0

Atomic builtins questions

by Yvan Roux

Hi, I think I have identified some issues with the atomic builtins, but I want your advises. For instance : A: __atomic_store_n (addr, val, __ATOMIC_SEQ_CST); gives the armv7 code: DMB sy STR r1, [r0] DMB sy but if I have well understood, the DMBs instructions only provide the property that the code is sequentially consistent, but not the atomicity for which we have to use the LDREX/STREX instructions. Thus I think that the code should be : DMB sy 1: LDREX r2, [r0] STREX r1, r2, [r0] TEQ r1, #0 BNE 1b B: __atomic_load_n (addr, __ATOMIC_ACQUIRE); gives the armv7 code: DMB sy LDR r0, [r0] but the load-acquire semantique specifies that all loads and stores appearing in program order after the load-acquire will be observed after the load-acquire, thus the DMB should be after the LDR, no ? -- Yvan

12 years, 9 months

3
7
0 0

ARMv8 load acquire / store release question

by Yvan Roux

Hi, I'm working on the libatomic-ops (part of the Boehm gc) AArch64 support, I mainly use GCC's __atomic builtins to do this, but in our 4.7 version they don't use the load acquire / store release instructions now available in the ARMv8 ISA. These instructions are used in the mainline GCC (in atomic.md) but not in their exclusive form, I understand that it should be due to the performance penalty, but I want your feeling on that point as I don't find the ARMv8 ISA really clear. If we want to implement an atomic load acquire, is LDAR x1, [x0] sufficient, or do we have to write it like that : L: LDAXR x0, [x3] STEX x1, x0, [x3] CBZ x0, L1 Thanks Yvan

12 years, 9 months

2
1
0 0

[MINUTES] Toolchain Performace Call 2012-11-27

by Matthew Gretton-Dann

All, [Editiorial: Michael & I discussed making what we do as a working group more visible at Connect. One thing we discussed was making our meeting minutes more visible by emailing actions out after each meeting. This will be part of the job of the 'minuter' - a job I plan to spread around as I am useless at it whilst also running a call - more info on the Wiki: https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings] The minutes of the performance call held on 27 November 2012 can be found at: https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2012-11-27 In summary the actions from the meting are: * mgrettondann split LRA blueprint * Christophe to update Hot/Cold partitioning bugzilla * mgrettondann: benchmark on Hold/Cold partitioning * Michael to log a ticket to improve reporting of benchmarks when the run complete. * Ramana to log EEMBC failure with Hot/Cold partitioning into bugzilla. * Christophe to backport bswap16 builtin, except for the testcase which fails in one of our configurations (Thumb1 + hard FP ABI) The next performance call will be on 11 December 2012 and the agenda can be found at: https://wiki.linaro.org/WorkingGroups/ToolChain/Meetings/2012-12-11 Thanks, Matt -- Matthew Gretton-Dann Linaro Toolchain Working Group matthew.gretton-dann(a)linaro.org

12 years, 9 months

2
1
0 0

[ANNOUNCE] Linaro Toolchain Binaries 2012.11 released

by Zhenqiang Chen

The Linaro Toolchain Working Group is pleased to announce the 2012.11 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 2012.11 * Linaro GDB 7.5 2012.09 * 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. 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/2012.11 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, 9 months

1
0
0 0

[Activity] Week 47

by Zhenqiang Chen

Summary: * Investigate shrink-wrap result. * Prepare for Linaro toolchain binary release, script merge and aarch64 test. Details: 1. Investigate shrink-wrap result of function Ray_In_Bound. By default, ARM/MIPS/PPC/X86 toolchain can not shrink-wrap the function. For ARM, there is copy "r6 = r1" which blocks the optimization. By hacking the assemble code, I got ~3% performance improvement for 453.povray benchmark. 2. Setup AARCH64 simulation environment by following http://www.linaro.org/engineering/armv8. 3. Write scripts to collect branch cost performance. It will take weeks to get all the benchmark results. 4. Smoke test Linaro toolchain binaries 2012.11 release. 5. Try export crosstool-ng trunk to a bzr project. bzr fast-import always fail on Ubuntu 10.04, but it works on 12.04. 6. RM toolchain related work. Plans: * Collect performance data for branch cost tuning. * Linaro binary toolchain 2012.11 release. * Verify shrink-wrap bugs. Best regards! -Zhenqiang

12 years, 9 months

1
0
0 0

[ACTIVITY] 19-23 November 2012

by Yvan Roux

== Progress == * Infrastructure: - Upgraded my laptop. * Boehm GC AArch64 support: - Added basic aarch64 support to libatomics (by use of GCC's atomics builtins). - Analysed testsuite results and the generated code. - Identified potential builtins' issues. * Some internal support. == Next == * Re-work libatomics support.

12 years, 9 months

1
0
0 0

[ACTIVITY] 19-23 November 2012

by Christophe Lyon

== Progress == * Turn off 64-bits bitops in Neon: initial implementation under benchmarking. Currently it modifies the handling of: add, sub, and, or, xor, shifts, not. In some case the generated code is quite larger, so it will careful benchmarking. * Started looking at "disable peeling" blue-print. Reading GCC source code to get more familiar with that area. * Internal support

12 years, 9 months

1
0
0 0

[ACTIVITY] report week 46

by Peter Maydell

* meetings/discussions + upcoming architecture & h/w features + virtio patchset review/discussion + 1-2-1 Matt, Michael + arndale board secondary CPU boot + naming conventions for v8 qemu + v7 KVM blueprint status + posture assessment + KVM call * thinking through possible corner cases for KVM with stage2 faults that don't tell the hypervisor the offending IPA * rebased qemu-linaro on qemu 1.3 rc0 * fixed upstream regression in "-usb" command line KVM blueprint progress tracker: http://ex.seabright.co.nz/helpers/backlog?group_by=topic&colour_by=state&pr… -- PMM

12 years, 9 months

1
0
0 0

[ACTIVITY] 19-23 November 2012

by Matthew Gretton-Dann

== Blueprints == Initial Current Actual initial-aarch64-backport 31 Oct 2012 30 Nov 2012 aarch64-baremetal-testing 31 Oct 2012 30 Nov 2012 fix-gcc-multiarch-testing 31 Dec 2012 31 Dec 2012 backport-fma-intrinsic 31 Dec 2012 31 Dec 2012 fused-multiply-add-support 31 Dec 2012 31 Dec 2012 gcc-investigate-lra-for-arm 31 Dec 2012 31 Dec 2012 == Progress == * Admin * Interviewing * Investigate patches for literal pool layout bug * Took longer than expected as the 'simple' fix is wrong due to GCC not knowing how large instructions actually are. * Patch posted upstream * Post triplet backport patches upstream * Other bug issues * Including an issue running SPEC2K on x86 with recent trunk == Next Week == * Run HOT/COLD partitioning benchmarks * Analyse ARM results * On x86_64 to see what the actual benefit we could get * initial-aarch64-backport & aarch64-baremetal-testing * Finish documentation * gcc-investigate-lra-for-arm * Analyse benchmarks * fix-gcc-multiarch-testing * Come up with strawman proposal for updating testsuite to handle testing with varying command-line options. == Future == * backport-fma-intrinsic & fused-multiply-add-support * Backport patches once fix-gcc-multiarch-testing has been done. -- Matthew Gretton-Dann Linaro Toolchain Working Group matthew.gretton-dann(a)linaro.org

12 years, 9 months

1
0
0 0

Shrink-wrap on povray

by Zhenqiang Chen

Hi, I try ARM, MIPS, PowerPC and X86 on povray benchmark. No one can shrink-wrap function Ray_In_Bound. Here is: bool Ray_In_Bound (RAY *Ray, OBJECT *Bounding_Object) { ... for (Bound = Bounding_Object; Bound != NULL; Bound = Bound->Sibling) {...} return (true); } For ARM O2/O3, "Bound" is allocated to "r6" during ira. So there is copy r6 = r1 before testing Bound != NULL The copy (using r6) blocks the shrink-wrap optimization since r6 should be saved. Need enhance shrink-wrap to handle this case. Overall, for povray benchmark, 54 functions are shrink-wrapped for ARM; 59 functions are shrink-wrapped for X86; 25 functions are shrink-wrapped for MIPS; 26 functions are shrink-wrapped for PowerPC. Thanks! -Zhenqiang

12 years, 9 months

2
5
0 0

Re: Re: Re: Re: unexpected reloc type 0x03 error with gcc-4.6.4 (2012.10 version)

by Michael Hope

On 15 November 2012 01:58, 남관우 <kw46.nam(a)samsung.com> wrote: > > Hi, > > > > As your guide, i tried to build again. > > > > without : -mapcs -fno-common -fstack-protector --param==ssp=buffer-size=4 > > > and -fPIC instead of -fpic > > > > But it is failed with same the message. (/usr/lib/libnfc-common-lib.so.1: unexpected reloc type 0x03) > > > > Thank you, > > Kwanwoo Nam. > > > > ------- Original Message ------- > > Sender : 남관우<kw46.nam(a)samsung.com> S4(선임)/선임/SLP개발그룹(무선)/삼성전자 > > Date : 2012-11-14 21:45 (GMT+09:00) > > Title : Re: Re: Re: unexpected reloc type 0x03 error with gcc-4.6.4 (2012.10 version) > > > > Hi, > > > > Here is our LDFLAGS. > > -Wl,--rpath=/usr/lib -Wl,--as-needed > > > > And i try to build with your guide. > > without : -mapcs -fno-common > and -fPIC instead of -fpic > > > > But it is failed with same the message. (/usr/lib/libnfc-common-lib.so.1: unexpected reloc type 0x03) Ta. I'm afraid we don't have enough information to solve this. Could you please send a full build log and we can go from there. gzipped on a public server is best. -- Michael

12 years, 9 months

2
2
0 0

[ACTIVITY] 12-16 November

by Matthew Gretton-Dann

== Blueprints == Initial Current Actual initial-aarch64-backport 31 Oct 2012 30 Nov 2012 aarch64-baremetal-testing 31 Oct 2012 30 Nov 2012 fix-gcc-multiarch-testing 31 Dec 2012 31 Dec 2012 backport-fma-intrinsic 31 Dec 2012 31 Dec 2012 fused-multiply-add-support 31 Dec 2012 31 Dec 2012 gcc-investigate-lra-for-arm 31 Dec 2012 31 Dec 2012 == Progress == * Admin * Interviewing * Hand over prep with Michael * Release Week * Made 2012.11 releases of gcc-linaro 4.6 and 4.7. * LEG interations: * Investigated CILK+ and how much work to port to AArch64. * HOT/COLD partitioning * Ran benchmarks on ARM * LRA * Ran x86-64 benchmarks == Next Week == * Investigate patches for literal pool layout bug * Post triplet backport patches upstream * Run HOT/COLD partitioning benchmarks * Analyse ARM results * On x86_64 to see what the actual benefit we could get * initial-aarch64-backport & aarch64-baremetal-testing * Finish documentation * gcc-investigate-lra-for-arm * Analyse benchmarks * fix-gcc-multiarch-testing * Come up with strawman proposal for updating testsuite to handle testing with varying command-line options. == Future == * backport-fma-intrinsic & fused-multiply-add-support * Backport patches once fix-gcc-multiarch-testing has been done. -- Matthew Gretton-Dann Linaro Toolchain Working Group matthew.gretton-dann(a)linaro.org

12 years, 9 months

1
0
0 0

[ACTIVITY] 11-16 November

by Yvan Roux

== Progress == * Infrastructure: - Managed to have my laptop re-installed by IT with a native Ubuntu 12.04, (as a beta tester). - Re-setup my working environment. * GCC release process familiarization. * Boehm GC AArch64 support: - Resume libatomic-ops work. * Some internal support == Next == * Continue on the Boehm GC AArch64 support.

12 years, 9 months

1
0
0 0

[Activity] Week 46

by Christophe Lyon

== Progress == * Started working on "Turn off 64 bits Bitops in Neon in GCC" blueprint. * branch review for aarch64-4.7 merge. A lot of time wasted due network instability making it difficult to checkout a GCC branch from launchpad/bzr. * Internal support for infrastructure problems. * Resumed discussions with our internal IT and Christian Bejram to try to decrease our constraints.

12 years, 10 months

1
0
0 0

[ACTIVITY] report week 46

by Peter Maydell

Progress: * card drafting for v8 QEMU work: commenting on Loic's draft cards, and drafting one for a 'v8 QEMU KVM prototype' as a foundation for both future KVM and QEMU system emulation work: http://cards.linaro.org/browse/CARD-214 http://cards.linaro.org/browse/CARD-215 http://cards.linaro.org/browse/CARD-217 http://cards.linaro.org/browse/CARD-221 * rebased qemu kvm patchset, updated to v14 kernel patches * added patch to align to allow transparent hugepage use * looking at v7 KVM blueprint status/planned work * investigating issues introduced by QEMU's attempts to use weak aliases / weak references in its build process * various standard meetings/calls * completed expenses claim for travel KVM blueprint progress tracker: http://ex.seabright.co.nz/helpers/backlog?group_by=topic&colour_by=state&pr… -- PMM

12 years, 10 months

1
0
0 0

[Activity] Week 46

by Zhenqiang Chen

Summary: * Benchmark tests for branch cost. Details: 1. Start branch cost tuning blueprint for A-profile (https://launchpad.net/gcc-linaro/+spec/gcc-linaro-improve-condexec). 2. Update Linaro crosstool-ng to support 2012.11 release. 3. RM toolchain related work. Leaves: * Nov. 12-13: Annual leaves Plans: * Collect performance data for different branch cost. * Prepare Linaro binary toolchain 2012.11 release Best regards! -Zhenqiang

12 years, 10 months

1
0
0 0

[ANNOUNCE] Linaro GCC 4.7 and Linaro GCC 4.6 2012.11 released

by Matthew Gretton-Dann

The Linaro Toolchain Working Group is pleased to announce the 2012.11 release of both Linaro GCC 4.7 and Linaro GCC 4.6. Linaro GCC 4.7 2012.11 is the eigth release in the 4.7 series. Based off the latest GCC 4.7.2+svn193200 release, it includes ARM-focused performance improvements and bug fixes. Interesting changes include: * Updates to GCC 4.7.2+svn193200 * Also includes arm/aarch64-4.7-branch up to svn revision 193328. Fixes: * LP #1065122 * LP #1065559 * LP #1067760 Linaro GCC 4.6 2012.11 is the 21st release in the 4.6 series. Based off the latest GCC 4.6.3+svn193199 release, this is the eigth release after entering maintenance. Interesting changes include: * Updates to 4.6.3+svn193199 The source tarballs are available from: https://launchpad.net/gcc-linaro/+milestone/4.7-2012.11 https://launchpad.net/gcc-linaro/+milestone/4.6-2012.11 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-2012.11 https://launchpad.net/gcc-linaro/4.6/4.6-2012.11 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 Linaro Toolchain Working Group matthew.gretton-dann(a)linaro.org

12 years, 10 months

1
0
0 0

Getting a broken program when the -funroll-loops flag is set (gcc linaro arm)

by Mickey Iluz

Hi, I've encountered a case where gcc produces a broken program: a branch that should never be taken is taken, and wrong values are written to memory (and printed out). The code is fairly ordinary and small. It can be seen here: http://pastebin.com/0Hspz8mw This happens when -funroll-loops flag is used in conjunction with -O2 or -O3. It doesn't seem to happen when it is used with -O1. Another few things that influences the program flow from from incorrect to correct run (gives expected outpus) are: - Adding/removing printf's inside the inner loop - Changing the order of the expressions in the "if" clause. i.e. from this: if ((y < mu) || (y >= H - md) || (x < ml) || (x >= W - mr)) to this: if ((x < ml) || (y >= H - md) || (y < mu) || (x >= W - mr)) - Assigning ml inside f() to the same value (3) it's getting from the function arguments. All of these shouldn't change how the program behaves but it does. I compiled this with two different compilers/environments: 1. g++ (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3, running on 3.2.1-42-linaro-lt-mx6 (native compilation on the ARM board) Compilation command: g++ -march=armv7-a -mfpu=neon -mfloat-abi=hard -mtune=cortex-a9 -O3 -std=c++0x -funroll-loops -o test_bug_sa_loops_linaro test_bug.cxx 2. arm-fsl-linux-gnueabi-g++ (Freescale MAD -- Linaro 2011.07 -- Built at 2011/08/10 09:20) 4.6.2 20110630 (prerelease) Running on a freescale LTIB built linux (3.0.15-1359-g1b64ead) Compilation command: arm-fsl-linux-gnueabi-g++ -march=armv7-a -mfpu=neon -mfloat-abi=hard -mtune=cortex-a9 -O3 -std=c++0x -funroll-loops -o test_bug_sa_loops test_bug.cxx In all the variations I tried it seems that -funroll-loops is critical for this problem to appear. I'd be glad to hear some comments on this. Mickey. This mail was sent via Mail-SeCure system.

12 years, 10 months

3
4
0 0

Fwd: Re: Re: Re: unexpected reloc type 0x03 error with gcc-4.6.4 (2012.10 version)

by 남관우

12 years, 10 months

1
0
0 0

Re: Re: Re: unexpected reloc type 0x03 error with gcc-4.6.4 (2012.10 version)

by 남관우

12 years, 10 months

1
0
0 0

Re: Compilation speed of Linaro's gcc compared to e.g. Ubuntu's version

by Michael Hope

On 10 November 2012 05:11, "Frank Müller" <franky1976(a)gmx.net> wrote: > Michael Hope <michael.hope(a)linaro.org>: >> My suspicion is that we/crosstool-NG enable extra features like >> Graphite or GCC is built with a different level of checking. If you > > I suspected Graphite as well and removed it in my own builds without noticable difference. > >> have the time, could you check the flags passed to GCCs configure? >> You can do this on Ubuntu using: >> >> apt-get build-dep gcc >> apt-get source gcc >> dpkg-buildpackage -uc -us -b >> >> and compare the configure line with the one in crosstool-NG's build.log. > > Isn't this the same as gcc -v? I've posted the lines at http://lists.linaro.org/pipermail/linaro-toolchain/2012-October/002913.html Good point. There's nothing obvious in the list. Ubuntu explicitly adds --enable-checking=release but it's the default for release branches like ours. I can reproduce the slowdown in a smaller testcase. Compiling pcre with -O3 -mfpu=neon -march=armv7-a -mtune=cortex-a8 takes 18.8 s for the Ubuntu Precise 4.6 compiler, 17.8 s for the Ubuntu Quantal 4.7 compiler, and 41.2 s for the Linaro 4.7 2012.10 build. I've logged LP: #1077739 to track. I'll spin a --enable-checking=release build just to check. > The above lines do not work for me, the last line misses a changelog file: > > # dpkg-buildpackage -uc -us -b > tail: cannot open `debian/changelog' for reading: No such file or directory > dpkg-buildpackage: error: tail of debian/changelog gave error exit status 1 Yip, you need to change to the just-extracted source directory first. -- Michael

12 years, 10 months

4
5
0 0

Re: Re: unexpected reloc type 0x03 error with gcc-4.6.4 (2012.10 version)

by Michael Hope

On 14 November 2012 00:48, 남관우 <kw46.nam(a)samsung.com> wrote: > > Hi, > > > > First, our CFLAGS is here. > > > > -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Wl,--as-needed > -fmessage-length=0 -march=armv7-a -mtune=cortex-a8 -mfpu=vfpv3-d16 -mfloat-abi=hard -mthumb -Wa,-mimplicit-it=thumb > -mapcs -mno-sched-prolog -mabi=aapcs-linux -Uarm -fno-common -fpic > > > > It was occurred with the message. (/usr/lib/libnfc-common-lib.so.1: unexpected reloc type 0x03) > > > > Second, > > -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -Wformat -Wformat-security -Wl,--as-needed > -fmessage-length=0 -march=armv7-a -mtune=cortex-a8 -mfpu=vfpv3-d16 -mfloat-abi=hard -mthumb -Wa,-mimplicit-it=thumb > -mapcs -mno-sched-prolog -fno-common -fpic > > > > It was occurred too. (/usr/lib/libnfc-common-lib.so.1: unexpected reloc type 0x03) Hi there. I don't know the cause but I'm suspicious of a few things. Could you try the following builds? The most likely: * Without -mapcs * Without -fstack-protector --param=ssp-buffer-size=4 Less likely: * Without -fno-common * With -fPIC instead of -fpic (should make no difference on ARM) Could you also send through the linker command line? It would be great to get a full log up on pastebin or similar. -- Michael

12 years, 10 months

1
0
0 0

Re: Re: unexpected reloc type 0x03 error with gcc-4.6.4 (2012.10 version)

by 남관우

12 years, 10 months

1
0
0 0

unexpected reloc type 0x03 error with gcc-4.6.4 (2012.10 version)

by Kyungmin Park

Hi Michael, Recently I tested the linaro toolchain gcc-4.6 version and try to build our codes. it's okay to compile the codes, but when launching the binary it occures following messages. /usr/lib/libnfc-common-lib.so.1: unexpected reloc type 0x03 I tested it both "hard float" and "soft float". the result is same. do you have any clues? Test environment: toolchain: gcc-4.6.4 (2012.10 version) soft float option. Thank you, Kyungmin Park

12 years, 10 months

2
2
0 0

linaro toolchain

by zhangzhangwei

hi, I use beaglebone ,and the CPU is AM3359 from TI can I use the linaro toolchain to the u-Boot linux kernel and android files?if I can ,which tool chain you suggest you use. other question, your android realese file also can use my CPU(AM3359),Can I build image and download to my SD and run it? thanks for your reply. zhangzhangwei 2012-11-09

12 years, 10 months

2
1
0 0

[ACTIVITY] 5 - 9 November

by Yvan Roux

== Progress == * Watched some Connect sessions (ARMv8, GCC performance) * AArch64 GDB support testing and backport investigation: - Activities blocked until patches with the pthread interface update are ready. * Boehm GC AArch64 support: - Read documentation on the garbage collector and ARMv8. - Asked for advices to the maintainers. - Started to port the libatomic_ops. == Next == * Continue on the Boehm GC AArch64 support.

12 years, 10 months

1
0
0 0

[ACTIVITY] report week 45

by Peter Maydell

* Attended LinuxCon Europe / ELC-Europe / QEMU Summit / KVM Forum (an overlapping set of conferences across a week in Barcelona) LCE/ELC: brief summary of interesting sessions (I've only listed ones which seem most relevant to ARM just to keep the length of this report down): * "Devicetree and its stumbling blocks" -- a view from a kernel developer perspective of some of the issues with doing platform data to dt conversions: (a) dt is supposedly OS independent and an external ABI, implying more need for cleanliness and long term supportable interfaces. (b) conversions imply a need to generalise bindings to be usable across many devices (c) what do we do about configuration / policy choices? My take is that the kernel folks are tying themselves in knots to try to preserve the (somewhat fictional in practice) idea that any kernel will work with any older device tree blob and they'd find it easier if they declared an amnesty for breaking changes before some deadline date... * Developing and testing industrial hardware with QEMU Rather than developing/testing sw against expensive/limited availability hw, use a model -- easier automation, ability to simulate error conditions, etc. If your hardware is basically a PCI card in an x86 box QEMU's fairly easy to use for this. * UEFI Secure Boot A summary of the current status of UEFI Secure Boot: it's mandatory for Win8 hardware; Linux implication is that we need to be able to maintain simple "out of box boot off distro CD"; optionally, if we have end-to-end signed binaries we have access to environments which will end up mandating it (read: government). Fortunately people have come together to tackle this and it looks like we're in good shape. http://mjg59.dreamwidth.org/18945.html is a good summary. * Kernel report by Jonathon Corbet ARM featured fairly prominently in this stats-driven roundup: 64-bit ARM support was first listed bullet point for 3.7 features Pointed out that Linaro and other embedded-ARM kernel contributions are notably up, ARM mess has been cleaned up. KVM Forum: * Concurrency in QEMU Plans for splitting QEMU's "big lock" into finer grained mutexes; should improve I/O scalability for KVM guests and realtime guest latency. However some tricky locking design issues to be solved. I am as usual sticking my oar in occasionally to remind people that the world is not solely x86-and-PCI... * qtest A summary of QEMU's new qtest framework, how it works and how to write tests. We're going to start insisting on test cases for new patches, so I need to write some basic tests for a few ARM devices so I know how it works :-) * ARM Virtualization for the Masses Christoffer Dall's talk introducing the ARM virt. extensions and KVM work. Well received, various questions afterwards (some elements of "why doesn't this work the way the x86 stuff does", also lots of "does this work on the Samsung/Google Chromebook" :-)) QEMU Summit: * This was an invite-only afternoon with perhaps 20 or so of the main QEMU contributors; broadly focused on "process" issues like release management, patch flow and security bug handling. Productive session; minutes should be available on the QEMU mailing list shortly. This is likely to be repeated next year. Informal discussions (IME the most important and worthwhile part): * virtio related : ran through current status of virtio-mmio patches with Anthony Liguori and Alex Graf, confirmed what changes we need to make and what the next steps with this should be. Some enthusiasm for getting this patchset in in the early part of the QEMU 1.4 release if we can. I'm really happy that we've unblocked this bit of work which had stalled slightly trying to figure out the right approach. Long term we will probably end up using virtio-pci on ARM but this is really dependent on hardware with good PCI support appearing. * SystemC : the upstream community is not currently interested in SystemC support, but there is some work on the QEMU core which would be a useful cleanup for QEMU itself and also useful for the SystemC folk. I'm hopeful that this might help to bring people working with QEMU in SystemC closer to the "QEMU upstream" community and mailing list, but it will be a gradual process both socially and technically if it does happen. * an informal enquiry about whether system emulation of virt. mode in ARM was planned or how much work it would be * in-kernel-irqchip: common ABI cross architecture the current ABI is a bit x86-specific, useful discussion about what POWER/S390/ARM would need. There will probably be some more ioctls coming along but the good news is that what the KVM ARM patches have currently fits into the proposals with only a very trivial tweak; we can add support for the new ioctls later if they are useful for us. -- PMM

12 years, 10 months

1
0
0 0

[ACTIVITY] 5 - 9 November

by Matthew Gretton-Dann

== Blueprints == Initial Current Actual initial-aarch64-backport 31 Oct 2012 30 Nov 2012 aarch64-baremetal-testing 31 Oct 2012 30 Nov 2012 fix-gcc-multiarch-testing 31 Dec 2012 31 Dec 2012 backport-fma-intrinsic 31 Dec 2012 31 Dec 2012 fused-multiply-add-support 31 Dec 2012 31 Dec 2012 gcc-investigate-lra-for-arm 31 Dec 2012 31 Dec 2012 == Progress == * Returned from Connect and followed up. * Updated performance blueprints for next iteration * Backporting Doko's triplet patches to 4.7 * Patches ready except for problems building Ada * HOT/COLD partitioning * Rebuilt with TBB/TBH disabled always * Started investigated LRA for ARM == Next Week == * Post triplet backport patches upstream * Run HOT/COLD partitioning benchmarks * On ARM to see if TBB/TBH is making the difference previously seen * On x86_64 to see what the actual benefit we could get * initial-aarch64-backport & aarch64-baremetal-testing * Finish documentation * gcc-investigate-lra-for-arm * Benchmark on x86_64 to see what the benfit could be. * fix-gcc-multiarch-testing * Come up with strawman proposal for updating testsuite to handle testing with varying command-line options. == Future == * backport-fma-intrinsic & fused-multiply-add-support * Backport patches once fix-gcc-multiarch-testing has been done. -- Matthew Gretton-Dann Linaro Toolchain Working Group matthew.gretton-dann(a)linaro.org

12 years, 10 months

1
0
0 0

Compilation speed of Linaro's gcc compared to e.g. Ubuntu's version

by "Frank Müller"

Dear all, we have an ARM Cortex-A8 board where we are running our application. I am in charge of maintaining the Linux on it and the toolchain/SDK setup. So far we've been running Poky/OpenEmbedded and using the cross compiler that came about during the compilation. For easier maintenance, we are now switching to Linaro. The image is set up and I can compile, however I notice a peculiar fact: the binary distribution of Linaro's gcc (https://launchpad.net/linaro-toolchain-binaries/trunk/2012.10/+download/gcc…) has a significantly larger compilation speed than a version of arm-linux-gnueabihf-gcc that is shipping with Ubuntu. In our particular case, using Ubuntu's version it takes less than 6 minutes to compile our software, but 10 minutes when we use Linaro's version. The makefiles and source are exactly the same, only the compiler is different. I also tried an older version (4.6) of Linaro's gcc to match the Ubuntu one (tested the 12.04 shipped version), with no significant difference. Compiler flags for the system are -march=armv7-a -mtune=cortex-a8 -mfpu=neon -mfloat-abi=hard Running with -ftime-report, most of the additional time seems to be spent in the parser. Adding -fno-graphite-identity -fno-graphite for Linaro's gcc did not make a difference. I believe I tried to use crosstool-ng to make my own version, but I don't remember the results as this was over 7 weeks ago. I also did not have a chance to compare performance of the binaries. I do notice a difference in compilation sizes (4.8 MB for Ubuntu's 4.6 version, 4.1 MB for Linaro's 4.7 versions - can't test anything other right now). I would like to use Linaro's gcc as the crosscompiler for our project, as it is an easy setup. Repackaging Ubuntu's version is an option, though (some of the team do not use Ubuntu, plus I'd like everybody to use EXACTLY the same version of the crosscompiler). So there is no real "problem" for me, per se, but I am extremely curious as to what is going on here. It seems that Linaro's gcc has additional patches or maybe just different default settings that cause additional time to be spent in the parser. It would be interesting to know what exactly this is and whether/how it can be disabled in those cases where time of compilation is more important than e.g. performance gain. TIA for replying. Best Frank

12 years, 10 months

3
7
0 0

Initial aarch64 plans

by Michael Hope

This is the first of a few Connect follow up emails. KVM and Cortex-A15 tuning are to come. Matt and I have entered the initial aarch64 blueprints. These are part of the bootstrap that clear the way for us and the community to port packages on top. The high priority ones are: * Add support for AArch64 to Boehm GC[1] * Add support for GProf to AArch64 backend of GCC[2] After those we have: * Add IFUNC support for AArch64[3] * AArch64 GCC support for Stack Protection[4] All are linked off the parent blueprint at: https://launchpad.net/gcc-linaro/+spec/aarch64-gcc-initial-meta and we'll add more there as time goes by. The plan is to commit to the first two and do them this iteration. The latter two aren't critical and will be done as part of our general work. -- Michael [1] https://launchpad.net/linaro-toolchain-misc/+spec/aarch64-boehm-gc [2] https://launchpad.net/gcc-linaro/+spec/aarch64-gcc-gprof-support [3] https://launchpad.net/binutils-linaro/+spec/aarch64-gcc-ifunc [4] https://launchpad.net/gcc-linaro/+spec/aarch64-gcc-ssp-support

12 years, 10 months

1
0
0 0

[ACTIVITY] report week 44

by Peter Maydell

* Attended Linaro Connect; notable sessions: + Ubuntu plans for QEMU for Ringtail release = upstream qemu has merged qemu-kvm back in so Ubuntu will switch to qemu from qemu-kvm for x86 = also makes sense now to use upstream qemu for all archs (following Debian) rather than using qemu-linaro for non-x86: reasons for using q-l in Ubuntu now mostly fixed (ie upstream ARM support no longer dire). Ubuntu will carry omap3 patches to avoid dropping that feature in the changeover = makes sense for Linaro too as we now have an automated package-to-PPA setup for people who need bleeding-edge and also will want Ubuntu to transition to a more stably released and supported QEMU codebase to use for KVM-on-ARM-servers + KVM Testing plans = worked through a list of things that would be nice to test; useful feedback from people in the session about what matters. Missing: specific commitment by anybody to write tests :-) + various informal discussions about possibilities for v8 QEMU * this week: at LinuxCon Europe / ELC-Europe / KVM-Forum / QEMU Summit -- PMM

12 years, 10 months

2
1
0 0

Daylight savings changes

by Michael Hope

Hi toolchain people, I've gone through and massaged our meetings and 1-on-1s to handle the recent daylight savings changes. Most meetings now start at 9:15 am GMT and 1-on-1s are packed before them if possible. Let me know if I should massage them further, -- Michael

12 years, 10 months

1
0
0 0

[ACTIVITY] 29 Oct - 2 Nov

by Matthew Gretton-Dann

== Progress == * Attended Linaro Connect * Worked out focus for performance in next iteration: * Cortex-A15 * Other discussions on: * Transitioning from cbuild->LAVA * ARMv8 GNU Tools support * big.LITTLE Toolchain tuning == Next Week == * Backport Doko's configury changes for arm-none-linux-gnueabihf support * Remerge HOT/COLD partitioning to test like for like (TBB generation) * Benchmark LRA vs Reload on x86 and x86-64 * Write up strawman for non-multitest testing in GCC == Future == * Decide whether the effort to develop HOT/COLD partitioning is worth it. * Support LRA on ARM. * Attend Connect in Hong Kong... -- Matthew Gretton-Dann Linaro Toolchain Working Group matthew.gretton-dann(a)linaro.org

12 years, 10 months

1
0
0 0

ARM cross mismatch error

by naveen yadav

Dear All, We have ARM cross compiler, and building our code. we got below error. we have GCC Linaro 4.6.4. arm-linux-gnueabi/bin/ld: DIV usage mismatch between /home/Release/libasm.a(Blt32_Neon.o) and /home/Release/liblayer.so arm-linux-gnueabi/bin/ld: failed to merge target specific data of file /home/Release/libasm.a(Blt32_Neon.o) is it related to below link ? http://sourceware.org/ml/binutils/2012-03/msg00211.html thanks

12 years, 10 months

2
1
0 0

Some ugly patches for gcc-linaro on Android

by Bernhard Rosenkränzer

Hi, here's some patches for gcc-linaro to make it work with --host=arm-linux-androideabi They're the quick and dirty thing to do and look like they could have been written by Microsoft, needed something working in time for Connect ;) gcc-4.7-android-workarounds.patch: Workarounds for things that go wrong, but where the true cause is yet to be determined (e.g. why would configure think we have fread_unlocked and friends when we don't?) gcc-4.7-libitm-android.patch: Workaround for Bionic not knowing Elf32_auxv_t gcc-4.7-no-unneeded-multilib.patch: Get the multilib config in sync with regular Linux gcc-4.7-stlport.patch: Use stlport instead of libstdc++ (yes, this sucks - but it's what Android decided to do). Still needs to link libstdc++ because Bionic contains a libstdc++.so (but it's more like a libsupc++ - no STL there, but needed for stlport to work). ttyl bero

12 years, 10 months

2
1
0 0

[ACTIVITY] 22-26 October

by Matthew Gretton-Dann

== Progress == * HOT/COLD partitioning for PGO * Initial look at results * Patch Tracking & Backporting * Testing Doko's configury changes for arm-none-linux-gnueabihf support * Connect Prep * LRA Investigations * Sign/zero extension II == Next Week == * Linaro Connect == Future == * Attend Connect * HOT/COLD partitioning for PGO: * Get two current patches accepted upstream * Post question upstream about register allocation 'mistakes' I am seeing -- Matthew Gretton-Dann Linaro Toolchain Working Group matthew.gretton-dann(a)linaro.org

12 years, 10 months

1
0
0 0

[Activity] Week 43

by Zhenqiang Chen

Summary: * Validate and release Linaro binary toolchain 2012.10 * Test Details: 1. Release Linaro binary toolchain 2012.10 * Fix windows installer issue due to version format change. * Validate and release Linaro binary toolchain 2012.10. 2. Identify the root cause of PR 54902 (lp:1065559), and Richard Biener fixed it. 3. Enable SPEC2006 test. Testing is ongoing. Planed Leaves: * Nov. 5-7: Off site teambuilding event. * Nov. 9, 12-13: Annual leaves Plans: * Performance test for shrink-wrap. Best regards! -Zhenqiang

12 years, 10 months

1
0
0 0

[Activity] October 22-26

by Christophe Lyon

== Progress == * PGO/hot-cold partitioning/Spec2k: * Debugging why 254.gap is causing an ICE. * Connect preparation: Still preparing a temporary laptop * Internal stuff == Next == * Connect

12 years, 10 months

1
0
0 0

[ACTIVITY] report week 43

by Peter Maydell

== track-kvm-abi-changes == * updated qemu patches to match Christoffer's v13 tree, committed all fixes suggested in previous round of code review, rebased and sent RFC v3 of the QEMU KVM/ARM support patches == other == * rebased qemu-linaro on master; found and fixed a bug which meant that beagle models crashed when the kernel tried to touch the USB-OHCI device * submitted some minor QEMU cleanup patches (last lot of stuff before softfreeze next week, I expect) * usual upstream review/etc * started to look at virtio-mmio patches * prep for Linaro Connect next week KVM blueprint progress tracker: http://ex.seabright.co.nz/helpers/backlog?group_by=topic&colour_by=state&pr… -- PMM

12 years, 10 months

1
0
0 0

[ACTIVITY] 22-26 October

by Yvan Roux

== Progress == * Aarch64 GDB support testing: - Ran the GDB testsuite via gdbserver on x86 - Made a board file to run against the model - Tried debugging a simple hello world via gdbserver: It fails while loading the image, because of a mismatch between kernel and GDB ptrace interface. * Aarch64 GDB backport investigation: - Backported to the Linaro GDB 7.5 release. - Discussed with ARM people the ptrace issue. == Next == * On vacation.

12 years, 10 months

1
0
0 0

[ANNOUNCE] Linaro Toolchain Binaries 2012.10 released

by Zhenqiang Chen

The Linaro Toolchain Working Group is pleased to announce the 2012.10 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 2012.10 * Linaro GDB 7.5 2012.09 * 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. 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/2012.10 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, 10 months

1
0
0 0

Test Case to verify the support of VFPV3 and VFPV4

by Jubi Taneja

Hi All, I wanted to see the difference in objdump of an application where I can make the difference between the VFPV3 and VFPV4 support. I tried enabling the flag -mfpu=vfpv3 and -mfpu=vfpv4 for ARM Cortex A15 toolchain in my test code but cannot see the difference in two objdumps. According to my survey, the fused multiply and accumulate is the only instruction that can create the difference in two. Can any one provide the sample test code for the same? Precisely, I wish to see the difference in performance for vfpv3 and vfpv4. Looking forward to your reply. Thanks and Regards, Jubi

12 years, 10 months

4
13
0 0

[Activity] Week 42

by Zhenqiang Chen

Summary: * Linaro bug analysis * Validation Details: 1. Linaro bug analysis: * lp:1065122: Triaged. A fix patch was committed to 4.7 and trunk. * lp:1065559: Confirmed. Need more investigation to find the root cause. * lP:1065509: Can not reproduce it with the latest Linaro toolchain. * lp:1066095: Investigate and invalid it since the reporter can not reproduce it now. 2. Bug fix and smoke test for Linaro binary toolchain 2012.10 release. 3. Clean up shrink-wrap related patches and send to Linaro mail-list for review. Plans: * Linaro binary toolchain 2012.10 release. * Shrink-wrap performance test. Planed leave: * Oct. 26 Best regards! -Zhenqiang

12 years, 10 months

1
0
0 0

[ACTIVITY] 15-19 October

by Yvan Roux

== Progress == * Read wikis on OpenEmbedded and FastModel * Aarch64 GDB support testing : - Managed to run OE rootfs and kernel under FastModel - Configured the ssh/scp access to the model * Aarch64 GDB backport investigation : - Discussed with ARM the port and plans - Identified upstream patches == Next == * Continue on Aarch64 GDB.

12 years, 10 months

1
0
0 0

[ACTIVITY] report week 42

by Peter Maydell

Short week (two days): == other == * implemented QEMU patches to track and tell the kernel where the various bits of the VGIC should be mapped in the address space; however these seem to cause the host kernel to Oops... * added a log message category for "guest just did something that's probably a bug in the guest", so we can use it instead of random printf/aborting QEMU * generate inline code for Neon 64 bit negate and 32 bit abs, rather than calling helper functions * updated and resent new versions of some minor cleanup patches which had got lost/obsoleted by QEMU internals changes KVM blueprint progress tracker: http://ex.seabright.co.nz/helpers/backlog?group_by=topic&colour_by=state&pr… -- PMM

12 years, 10 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain