Use -O2 instead -O3 for Android build.

Use -O2 instead -O3 for Android build.

It produces smaller binary with almost the same performance.

R=benm@chromium.org, jkummerow@chromium.org

Committed: https://code.google.com/p/v8/source/detail?r=15071

[ulan, 2013-06-05 09:23:24]

Please take a look. Ben measured that this saves ~250K of binary size. Our perf
bots and local tests show no significant difference on performance.

We will revert it if this regresses chromium perf bots.

[Jakob Kummerow, 2013-06-05 09:25:21]

lgtm

https://chromiumcodereview.appspot.com/15929009/diff/1/build/android.gypi
File build/android.gypi (right):

https://chromiumcodereview.appspot.com/15929009/diff/1/build/android.gypi#new...
build/android.gypi:79: '-O3',
Actually, I think you can delete everything here that's just a copy of
common.gypi anyway (AFAICS, the entire 'Release' section except for
'-fomit-frame-pointer').

[ulan, 2013-06-05 09:30:59]

https://chromiumcodereview.appspot.com/15929009/diff/1/build/android.gypi
File build/android.gypi (right):

https://chromiumcodereview.appspot.com/15929009/diff/1/build/android.gypi#new...
build/android.gypi:79: '-O3',
On 2013/06/05 09:25:21, Jakob wrote:
> Actually, I think you can delete everything here that's just a copy of
> common.gypi anyway (AFAICS, the entire 'Release' section except for
> '-fomit-frame-pointer').

Done.

[benm (inactive), 2013-06-05 09:36:50]

lgtm

thanks Ulan!

[benm (inactive), 2013-06-10 17:55:34]

On 2013/06/05 09:36:50, benm wrote:
> lgtm
> 
> thanks Ulan!

ping?

[ulan, 2013-06-11 08:09:01]

I am going to land and roll it to chromium as a single-point release, so that we
know its impact on chromium bots. But before that we need to fix another issue
with kraken benchmark:
https://code.google.com/p/chromium/issues/detail?id=248076

[ulan, 2013-06-12 08:05:50]

Committed patchset #3 manually as r15071 (presubmit successful).