Revert of Change //build/config/compiler:optimize_max to use -O3.

Revert of Change //build/config/compiler:optimize_max to use -O3. (patchset #1 id:1 of https://codereview.chromium.org/2048163002/ )

Reason for revert:
Reverting, this caused a size regression for cronet that is more important to them than any likely perf gains.

I'll re-land a different CL that's less broad.

Original issue's description:
> Change //build/config/compiler:optimize_max to use -O3.
>
> Certain components (e.g., v8) really want to be compiled with -O3,
> but the current ":optimize_max" setting just used -O2. Since "max"
> should theoretically mean "max", let's try making it be -O3 across
> the board and see what happens.
>
> R=brettw@chromium.org
> BUG=616031
>
> Committed: https://crrev.com/96a6dfa2c30ab9b22abd20c87ed0e0d6ae41c40e
> Cr-Commit-Position: refs/heads/master@{#398704}

TBR=brettw@chromium.org,machenbach@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=616031
Committed: https://crrev.com/c4dc398543c8a7cbd4b5f8bfe3495d6182dc3f19
Cr-Commit-Position: refs/heads/master@{#399276}

[Dirk Pranke, 2016-06-10 20:00:34]

The CQ bit was checked by dpranke@chromium.org

[Dirk Pranke, 2016-06-10 20:00:34]

Created Revert of Change //build/config/compiler:optimize_max to use -O3.

[commit-bot: I haz the power, 2016-06-10 20:00:57]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2062433002/1

[brettw, 2016-06-10 20:59:43]

lgtm

[commit-bot: I haz the power, 2016-06-10 21:41:32]

Description was changed from

==========
Revert of Change //build/config/compiler:optimize_max to use -O3. (patchset #1
id:1 of https://codereview.chromium.org/2048163002/ )

Reason for revert:
Reverting, this caused a size regression for cronet that is more important to
them than any likely perf gains.

I'll re-land a different CL that's less broad.

Original issue's description:
> Change //build/config/compiler:optimize_max to use -O3.
> 
> Certain components (e.g., v8) really want to be compiled with -O3,
> but the current ":optimize_max" setting just used -O2. Since "max"
> should theoretically mean "max", let's try making it be -O3 across
> the board and see what happens.
> 
> R=brettw@chromium.org
> BUG=616031
> 
> Committed: https://crrev.com/96a6dfa2c30ab9b22abd20c87ed0e0d6ae41c40e
> Cr-Commit-Position: refs/heads/master@{#398704}

TBR=brettw@chromium.org,machenbach@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=616031
==========

to

==========
Revert of Change //build/config/compiler:optimize_max to use -O3. (patchset #1
id:1 of https://codereview.chromium.org/2048163002/ )

Reason for revert:
Reverting, this caused a size regression for cronet that is more important to
them than any likely perf gains.

I'll re-land a different CL that's less broad.

Original issue's description:
> Change //build/config/compiler:optimize_max to use -O3.
> 
> Certain components (e.g., v8) really want to be compiled with -O3,
> but the current ":optimize_max" setting just used -O2. Since "max"
> should theoretically mean "max", let's try making it be -O3 across
> the board and see what happens.
> 
> R=brettw@chromium.org
> BUG=616031
> 
> Committed: https://crrev.com/96a6dfa2c30ab9b22abd20c87ed0e0d6ae41c40e
> Cr-Commit-Position: refs/heads/master@{#398704}

TBR=brettw@chromium.org,machenbach@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=616031
==========

[commit-bot: I haz the power, 2016-06-10 21:41:33]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-10 21:41:50]

CQ bit was unchecked

[commit-bot: I haz the power, 2016-06-10 21:43:25]

Description was changed from

==========
Revert of Change //build/config/compiler:optimize_max to use -O3. (patchset #1
id:1 of https://codereview.chromium.org/2048163002/ )

Reason for revert:
Reverting, this caused a size regression for cronet that is more important to
them than any likely perf gains.

I'll re-land a different CL that's less broad.

Original issue's description:
> Change //build/config/compiler:optimize_max to use -O3.
> 
> Certain components (e.g., v8) really want to be compiled with -O3,
> but the current ":optimize_max" setting just used -O2. Since "max"
> should theoretically mean "max", let's try making it be -O3 across
> the board and see what happens.
> 
> R=brettw@chromium.org
> BUG=616031
> 
> Committed: https://crrev.com/96a6dfa2c30ab9b22abd20c87ed0e0d6ae41c40e
> Cr-Commit-Position: refs/heads/master@{#398704}

TBR=brettw@chromium.org,machenbach@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=616031
==========

to

==========
Revert of Change //build/config/compiler:optimize_max to use -O3. (patchset #1
id:1 of https://codereview.chromium.org/2048163002/ )

Reason for revert:
Reverting, this caused a size regression for cronet that is more important to
them than any likely perf gains.

I'll re-land a different CL that's less broad.

Original issue's description:
> Change //build/config/compiler:optimize_max to use -O3.
>
> Certain components (e.g., v8) really want to be compiled with -O3,
> but the current ":optimize_max" setting just used -O2. Since "max"
> should theoretically mean "max", let's try making it be -O3 across
> the board and see what happens.
>
> R=brettw@chromium.org
> BUG=616031
>
> Committed: https://crrev.com/96a6dfa2c30ab9b22abd20c87ed0e0d6ae41c40e
> Cr-Commit-Position: refs/heads/master@{#398704}

TBR=brettw@chromium.org,machenbach@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=616031

Committed: https://crrev.com/c4dc398543c8a7cbd4b5f8bfe3495d6182dc3f19
Cr-Commit-Position: refs/heads/master@{#399276}
==========

[commit-bot: I haz the power, 2016-06-10 21:43:26]

Patchset 1 (id:??) landed as
https://crrev.com/c4dc398543c8a7cbd4b5f8bfe3495d6182dc3f19
Cr-Commit-Position: refs/heads/master@{#399276}