Re: Evaluate Link Time Optimization (LTO) in linaro-gcc 4.5

2011-03-21 Thread Ramana Radhakrishnan
> $ arm-eabi-gcc -c -mfloat-abi=softfp -mfpu=neon -flto > -user-linker-plugin -c neon-intrinsics.c > neon-intrinsics.c:7:1: sorry, unimplemented: gimple bytecode streams > do not support machine specific builtin functions on this target I think this is because the Neon intrinsics are not streamed

Re: Evaluate Link Time Optimization (LTO) in linaro-gcc 4.5

2011-03-20 Thread Jim Huang
On 21 March 2011 06:01, Michael Hope wrote: > On Mon, Mar 21, 2011 at 4:25 AM, Jim Huang wrote: [...] >> The build process would be interrupted by gcc: >> make -j4 --warn-undefined-variables -f ../scripts/build/main.mk >> TOOLCHAIN=/tmp/android-toolchain-eabi ADD_CFLAGS="-flto >> -user-linker-plu

Re: Evaluate Link Time Optimization (LTO) in linaro-gcc 4.5

2011-03-20 Thread Michael Hope
On Mon, Mar 21, 2011 at 4:25 AM, Jim Huang wrote: > Hello list, > > Recently, Android team is working on integrating Linaro toolchain for > Android and NDK.  According to the initial benchmark results[1], > Linaro GCC is competitive comparing to Google toolchain.  In the > meanwhile, we are trying

Evaluate Link Time Optimization (LTO) in linaro-gcc 4.5

2011-03-20 Thread Jim Huang
Hello list, Recently, Android team is working on integrating Linaro toolchain for Android and NDK. According to the initial benchmark results[1], Linaro GCC is competitive comparing to Google toolchain. In the meanwhile, we are trying to enable gcc-4.5 specific features such as Graphite and LTO