All Credit got to the CM team and Sbrissen who got CM working for our phones
Compiled with Linaro's GCC 4.7.3 toolchain (01/13)
Compiled with Linaro GCC 4.6.2
Updated wifi driver
Unofficial Voodoo sound driver (otherwise this has not been reviewed and approved by Supercurio)
OverClock up to 1.8 Ghz
Downgrade to mali r2p4 which fixed graphic glitches
Kernel source - https://github.com/kejar31/android_k...msung_smdk4412
Boot to recovery and make a backup
Quick rundown from a Phoronix artificial that does a pretty good job of a quick breakdown on the differences.. It even includes some benchmarks
Note that Android is normally compiled with O2 and Os
For those unfamiliar with the different optimization flags, see the GCC optimize options documentation. The tested flags used in this article include:
-O0 - Reduce compilation time and make debugging produce the expected results. This is the default.
-O1 - Optimize. Optimizing compilation takes somewhat more time, and a lot more memory for a large function.
-O2 - Optimize even more. GCC performs nearly all supported optimizations that do not involve a space-speed tradeoff. As compared to -O, this option increases both compilation time and the performance of the generated code.
-O3 - Optimize yet more. -O3 turns on all optimizations specified by -O2 and also turns on the -finline-functions, -funswitch-loops, -fpredictive-commoning, -fgcse-after-reload, -ftree-vectorize, -fvect-cost-model, -ftree-partial-pre and -fipa-cp-clone options.
-Os - Optimize for size. -Os enables all -O2 optimizations that do not typically increase code size. It also performs further optimizations designed to reduce code size.
-Ofast - Disregard strict standards compliance. -Ofast enables all -O3 optimizations. It also enables optimizations that are not valid for all standard-compliant programs. It turns on -ffast-math and the Fortran-specific -fno-protect-parens and -fstack-arrays.