[ROM]CM10.1 Linaro O3 Build With Basic Kernel 02/04

Search This thread

kejar31

Inactive Recognized Developer
May 24, 2010
1,961
2,442
Thought I would share this. Its a build of CM10.1 from 02/04 with the Linaro updates added and compiled with linaro's 4.7 toolchain oh and it had O3 turned on :)

All Credit got to the CM team and Sbrissen who got CM working for our phones


Features:

ROM
Compiled with Linaro's GCC 4.7.3 toolchain (01/13)
O3

KERNEL
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
CPU Undervolting
Downgrade to mali r2p4 which fixed graphic glitches

Source:
Kernel source - https://github.com/kejar31/android_k...msung_smdk4412

Credit:
gokhanmoral
codeworkx
sbrissen
CyanogenMod
supercurio
Tk-Glitch

Install:
Boot to recovery and make a backup
Wipe data/cache/dalvik
Flash ROM
Flash GAPPS
Reboot

Downlaods:
GAPPS

L900 (SPR)




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.
 

kejar31

Inactive Recognized Developer
May 24, 2010
1,961
2,442
How is this any different from Liquid Smooth?

Sent from my SPH-L900 using Xparent Skyblue Tapatalk 2

This is CM10.1 with only the needed changes to allow -O3 and GCC 4.7 plus BasicKernel (my kernel)..

Liquid Smooth using an entirely different base with their own options etc...
 
  • Like
Reactions: Paiyne

Top Liked Posts

  • There are no posts matching your filters.
  • 16
    Thought I would share this. Its a build of CM10.1 from 02/04 with the Linaro updates added and compiled with linaro's 4.7 toolchain oh and it had O3 turned on :)

    All Credit got to the CM team and Sbrissen who got CM working for our phones


    Features:

    ROM
    Compiled with Linaro's GCC 4.7.3 toolchain (01/13)
    O3

    KERNEL
    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
    CPU Undervolting
    Downgrade to mali r2p4 which fixed graphic glitches

    Source:
    Kernel source - https://github.com/kejar31/android_k...msung_smdk4412

    Credit:
    gokhanmoral
    codeworkx
    sbrissen
    CyanogenMod
    supercurio
    Tk-Glitch

    Install:
    Boot to recovery and make a backup
    Wipe data/cache/dalvik
    Flash ROM
    Flash GAPPS
    Reboot

    Downlaods:
    GAPPS

    L900 (SPR)




    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.
    2
    What are the bugs for this rom?

    Sent from my Note II

    same as CM10.1 nightly's
    1
    How is this any different from Liquid Smooth?

    Sent from my SPH-L900 using Xparent Skyblue Tapatalk 2

    This is CM10.1 with only the needed changes to allow -O3 and GCC 4.7 plus BasicKernel (my kernel)..

    Liquid Smooth using an entirely different base with their own options etc...