[ACTIVITY] 4-8 Feb 2013
== Progress == * February merge 4.6 and 4.7 - backport a patch from upstream to resolve conflicts - this backport introduced some merge issues - fix pushed and merge request ongoing * Boehm GC AArch64 support: - libatomic_ops maintainer rework the patch to make the usage of gcc atomic builtins available on the other targets - test exhibit some failures * libunwind aarch64 support - bug status moved to critical - configuration and machine description done - implementation ongoing * Aarch64 porting meeting: - Cancelled this week == Next == * February merge 4.6 and 4.7 - log new testsuite failures in launchpad * Boehm GC AArch64 support: - fix libatomic_ops - validate GCC's Boehm gc integration * libunwind aarch64 support - conitnue. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] 4th Feb 2013 - 8th Feb 2013
== This Week === * Tried running GDB test suite with QEMU linux user-mode with not much success * Configured Pandaboard and ran GDB test suite in native and native-gdbserver configurations. * More of office setup and purchase of some bits and pieces * Gateway set up and Pandaboard access finally worked after some help from Dave and Matt. * Finally purchased Ticket for the Connect and also filled visa application * Attended Weekly toolchain call * Still suffering from a bad run of cough n flu, done with antibiotics now. * Public Holiday on 5th Feburary == Next week == * Continue with Analysis of GDB status on ARM in different configurations possible. * SSH tunnels and port forwarding setup to gateway and lab for smooth access. * Follow up on hong kong visa application ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] 4-8 Feb 2013
== Progress == * 64-bits ops in Neon: upstream accepted the patch for gcc-4.9-stage1 * smin-umin: several benchmarks runs necessary to confirm that the generic patch I suspected actually caused the regression. However, it also brings improvements in other benches (office-type). * looked at libasan: very little configuration seems necessary, but running a sample program under qemu leads to asan runtime complains. * internal tasks == Next == * smin-umin: run benchmarks on trunk to confirm the regression is also present. * vectorizer cost model: handle Richard's feedback. * get more codecs sample codes. * libasan: understand error messages Christophe. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Hard Floating Point Question
Derek Rollend writes: > > Hello, > I am currently trying to determine how much I can optimize OpenCV using the >ARM's VFP and the Linaro nano image. I have downloaded the >arm-linux-gnueabihf-gcc & arm-linux-gnueabihf-g++ compilers, successfully >cross-compiled OpenCV using those compilers (with -O3 -mfloat-abi=hard >-ftree-vectorize -funroll-loops), and compiled an example OpenCV program with >the arm-linux-gnueabihf-g++ compiler (with the same flags). Hello Derek, I'm trying to cross compile OpenCV (2.4.0) for ARM. I'm using Linaro toolchain and CMake (http://processors.wiki.ti.com/index.php/Building_OpenCV_for_ARM_Cortex-A8), but I get the following error: .../ffmpeg_codecs.hpp:78:36:fatal error: libavformat/avformat.h: No such file or directory compilation terminated. I have installed libavformat-dev and configured CMake again, but I get the same error. Which version of CMake you are using? How you write de toolchain.cmake? How do you set the (-O3 -mfloat-abi=hard -ftree-vectorize -funroll-loops) C/CXX flags? I'm using CMake2.8.7. Thanks in advance. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Hard Floating Point Question
Fernan, I'm using CMake 2.8.0. I have not tried to compile OpenCV with FFMPEG support yet, although I will be trying to do this soon. I have only successfully compiled OpenCV 2.2 using the Linaro hard float compiler. Here is my toolchain.cmake file: set( CMAKE_SYSTEM_NAME Linux ) set( CMAKE_SYSTEM_PROCESSOR arm ) set( CMAKE_C_COMPILER arm-linux-gnueabihf-gcc ) set( CMAKE_CXX_COMPILER arm-linux-gnueabihf-g++ ) set( CMAKE_CXX_FLAGS_RELEASE "-L /opt/gcc-linaro-arm-linux-gnueabihf-4.7-2013.01-20130125_linux/arm-linux-gnueabihf/lib -O3 -mcpu=cortex-a8 -mfpu=neon -mfloat-abi=hard -ftree-vectorize -ftree-vectorizer-verbose=3 -funroll-loops" ) set( CMAKE_CXX_FLAGS_DEBUG "-L /opt/gcc-linaro-arm-linux-gnueabihf-4.7-2013.01-20130125_linux/arm-linux-gnueabihf/lib -O3 -mcpu=cortex-a8 -mfpu=neon -mfloat-abi=hard -ftree-vectorize -ftree-vectorizer-verbose=3 -funroll-loops" ) where the Linaro hard float toolchain tarball was extracted to my /opt directory. The verbose flag will tell you when the compiler was able to vectorize a loop, or why it couldn't. I need to test some of the newer feature extraction algorithms in more recent versions of OpenCV, so I'll try and update you when/if I successfully compile a newer version of OpenCV with FFMPEG support. Good luck. -Derek On Mon, Feb 11, 2013 at 3:07 PM, Fernan wrote: > Derek Rollend writes: > > > > > Hello, > > I am currently trying to determine how much I can optimize OpenCV using > the > >ARM's VFP and the Linaro nano image. I have downloaded the > >arm-linux-gnueabihf-gcc & arm-linux-gnueabihf-g++ compilers, successfully > >cross-compiled OpenCV using those compilers (with -O3 -mfloat-abi=hard > >-ftree-vectorize -funroll-loops), and compiled an example OpenCV program > with > >the arm-linux-gnueabihf-g++ compiler (with the same flags). > > Hello Derek, > I'm trying to cross compile OpenCV (2.4.0) for ARM. I'm using Linaro > toolchain > and CMake > (http://processors.wiki.ti.com/index.php/Building_OpenCV_for_ARM_Cortex-A8), > but > I get the following error: > .../ffmpeg_codecs.hpp:78:36:fatal error: libavformat/avformat.h: No such > file or > directory > compilation terminated. > I have installed libavformat-dev and configured CMake again, but I get the > same > error. > Which version of CMake you are using? > How you write de toolchain.cmake? > How do you set the (-O3 -mfloat-abi=hard -ftree-vectorize -funroll-loops) > C/CXX > flags? > I'm using CMake2.8.7. > Thanks in advance. > > > > > > > ___ > linaro-toolchain mailing list > linaro-toolchain@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-toolchain > ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Hard Floating Point Question
Derek Rollend writes: > > > Fernan, > I'm using CMake 2.8.0. I have not tried to compile OpenCV with FFMPEG support yet, although I will be trying to do this soon. I have only successfully compiled OpenCV 2.2 using the Linaro hard float compiler. Here is my toolchain.cmake file: > > > set( CMAKE_SYSTEM_NAME Linux ) > set( CMAKE_SYSTEM_PROCESSOR arm ) > set( CMAKE_C_COMPILER arm-linux-gnueabihf-gcc ) > set( CMAKE_CXX_COMPILER arm-linux-gnueabihf-g++ ) > set( CMAKE_CXX_FLAGS_RELEASE "-L >/opt/gcc-linaro-arm-linux-gnueabihf-4.7-2013.01-20130125_linux/ >arm-linux-gnueabihf/lib -O3 -mcpu=cortex-a8 -mfpu=neon -mfloat-abi=hard >-ftree-vectorize -ftree-vectorizer-verbose=3 -funroll-loops" ) > set( CMAKE_CXX_FLAGS_DEBUG "-L /opt/gcc-linaro-arm-linux-gnueabihf- >4.7-2013.01-20130125_linux/arm-linux-gnueabihf/lib >-O3 -mcpu=cortex-a8 -mfpu=neon -mfloat-abi=hard -ftree-vectorize >-ftree-vectorizer-verbose=3 -funroll-loops" ) > Thank you very much Derek, some questions arises reading your response, e.g. How Cmake knows the PATH of arm-linux-gnueabihf-g++? But now I will try to cross-compile again using your toolchain.cmake. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Hard Floating Point Question
Add the Linaro toolchain bin directory to your PATH environment variable: export PATH="/opt/gcc-linaro-arm-linux-gnueabihf-4.7-2013.01-20130125_linux/bin:$PATH" or whichever directory you have extracted the Linaro HF tarball to. -Derek On Mon, Feb 11, 2013 at 4:04 PM, Fernan wrote: > Derek Rollend writes: > > > > > > > Fernan, > > I'm using CMake 2.8.0. I have not tried to compile OpenCV with FFMPEG > support > yet, although I will be trying to do this soon. I have only successfully > compiled OpenCV 2.2 using the Linaro hard float compiler. Here is my > toolchain.cmake file: > > > > > > set( CMAKE_SYSTEM_NAME Linux ) > > set( CMAKE_SYSTEM_PROCESSOR arm ) > > set( CMAKE_C_COMPILER arm-linux-gnueabihf-gcc ) > > set( CMAKE_CXX_COMPILER arm-linux-gnueabihf-g++ ) > > set( CMAKE_CXX_FLAGS_RELEASE "-L > >/opt/gcc-linaro-arm-linux-gnueabihf-4.7-2013.01-20130125_linux/ > >arm-linux-gnueabihf/lib -O3 -mcpu=cortex-a8 -mfpu=neon -mfloat-abi=hard > >-ftree-vectorize -ftree-vectorizer-verbose=3 -funroll-loops" ) > > set( CMAKE_CXX_FLAGS_DEBUG "-L /opt/gcc-linaro-arm-linux-gnueabihf- > >4.7-2013.01-20130125_linux/arm-linux-gnueabihf/lib > >-O3 -mcpu=cortex-a8 -mfpu=neon -mfloat-abi=hard -ftree-vectorize > >-ftree-vectorizer-verbose=3 -funroll-loops" ) > > > > Thank you very much Derek, > some questions arises reading your response, e.g. How Cmake knows the PATH > of > arm-linux-gnueabihf-g++? > > But now I will try to cross-compile again using your toolchain.cmake. > > > > ___ > linaro-toolchain mailing list > linaro-toolchain@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-toolchain > ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
