By: Wilco (Wilco.Dijkstra.delete@this.ntlworld.com), July 18, 2013 5:18 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. It looks like AnTuTu just used the default NDK flags.
>
> http://code.google.com/p/android/issues/detail?id=56951
Those are stupid settings indeed. The old days of ARM is for performance and Thumb(-1) is for codesize are long gone...
However it is standard benchmarking practice to make all compiler options explicit rather than using some random unspecified default configuration. That way you can always reproduce the results with a different compiler version or different defaults. This is especially relevant for GCC as you can select different defaults when configuring it.
Wilco
> 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. It looks like AnTuTu just used the default NDK flags.
>
> http://code.google.com/p/android/issues/detail?id=56951
Those are stupid settings indeed. The old days of ARM is for performance and Thumb(-1) is for codesize are long gone...
However it is standard benchmarking practice to make all compiler options explicit rather than using some random unspecified default configuration. That way you can always reproduce the results with a different compiler version or different defaults. This is especially relevant for GCC as you can select different defaults when configuring it.
Wilco