By: Michael S (already5chosen.delete@this.yahoo.com), July 18, 2013 6:44 am
Room: Moderated Discussions
none (none.delete@this.none.com) on July 18, 2013 4:15 am wrote:
> Wilco (Wilco.Dijkstra.delete@this.ntlworld.com) on July 18, 2013 4:07 am wrote:
> [...]
> > Note that AnTuTu decided to go back to using GCC in their next version. Hopefully
> > they also manage to find the -O3 option in GCC, not easy I know...
>
> I hope Google will find it too.
I hope they don't.
gcc -O3 is way to aggressive to be a default.
For default I'd take something like "-O2 -fno-strict-aliasing".
> It looks like AnTuTu just used the default NDK flags.
>
> http://code.google.com/p/android/issues/detail?id=56951
>
>
> Wilco (Wilco.Dijkstra.delete@this.ntlworld.com) on July 18, 2013 4:07 am wrote:
> [...]
> > Note that AnTuTu decided to go back to using GCC in their next version. Hopefully
> > they also manage to find the -O3 option in GCC, not easy I know...
>
> I hope Google will find it too.
I hope they don't.
gcc -O3 is way to aggressive to be a default.
For default I'd take something like "-O2 -fno-strict-aliasing".
> It looks like AnTuTu just used the default NDK flags.
>
> http://code.google.com/p/android/issues/detail?id=56951
>
>