Revert of add --gdb-index to linker

Revert of add --gdb-index to linker (patchset #2 id:20001 of https://codereview.chromium.org/1680943002/ )

Reason for revert:
We suspect this may be causing an increase in binary size on some chromeos PFQ builders. Reverting to see if this is the cause.

Original issue's description:
> add --gdb-index to linker
>
> gold linker has a flag to automatically generate gdb-index section
> inside shared libraries when linking.
>
> Webkit single-file compile/linking time:
>
> 16.31s without gdb-index
> 16.11s with gdb-index
>
> gdb startup time
>
> ~51s without gdb-index
> ~19s with gdb-index
>
> BUG=
>
> Committed: https://crrev.com/f68b7c07a30baac088b8eda055ba52835c04692c
> Cr-Commit-Position: refs/heads/master@{#378600}

TBR=dpranke@chromium.org,thakis@chromium.org,atotic@google.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=

Committed: https://crrev.com/b3521bc11841b49542d4b4c6a415167202ae151b
Cr-Commit-Position: refs/heads/master@{#379165}

[stevenjb, 2016-03-03 22:28:29]

Created Revert of add --gdb-index to linker

[commit-bot: I haz the power, 2016-03-03 22:29:07]

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

[commit-bot: I haz the power, 2016-03-03 22:32:29]

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

[Dirk Pranke, 2016-03-03 22:34:29]

lgtm. We can make this be desktop linux-only and/or debug-only as needed if this
is a problem.

[commit-bot: I haz the power, 2016-03-03 23:01:39]

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

[commit-bot: I haz the power, 2016-03-03 23:31:44]

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

[commit-bot: I haz the power, 2016-03-04 00:01:55]

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

[commit-bot: I haz the power, 2016-03-04 00:31:48]

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

[commit-bot: I haz the power, 2016-03-04 01:01:41]

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

[commit-bot: I haz the power, 2016-03-04 01:30:24]

Description was changed from

==========
Revert of add --gdb-index to linker (patchset #2 id:20001 of
https://codereview.chromium.org/1680943002/ )

Reason for revert:
We suspect this may be causing an increase in binary size on some chromeos PFQ
builders. Reverting to see if this is the cause.


Original issue's description:
> add --gdb-index to linker
> 
> gold linker has a flag to automatically generate gdb-index section
> inside shared libraries when linking.
> 
> Webkit single-file compile/linking time:
> 
> 16.31s without gdb-index
> 16.11s with gdb-index
> 
> gdb startup time
> 
> ~51s without gdb-index
> ~19s with gdb-index
> 
> BUG=
> 
> Committed: https://crrev.com/f68b7c07a30baac088b8eda055ba52835c04692c
> Cr-Commit-Position: refs/heads/master@{#378600}

TBR=dpranke@chromium.org,thakis@chromium.org,atotic@google.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=
==========

to

==========
Revert of add --gdb-index to linker (patchset #2 id:20001 of
https://codereview.chromium.org/1680943002/ )

Reason for revert:
We suspect this may be causing an increase in binary size on some chromeos PFQ
builders. Reverting to see if this is the cause.


Original issue's description:
> add --gdb-index to linker
> 
> gold linker has a flag to automatically generate gdb-index section
> inside shared libraries when linking.
> 
> Webkit single-file compile/linking time:
> 
> 16.31s without gdb-index
> 16.11s with gdb-index
> 
> gdb startup time
> 
> ~51s without gdb-index
> ~19s with gdb-index
> 
> BUG=
> 
> Committed: https://crrev.com/f68b7c07a30baac088b8eda055ba52835c04692c
> Cr-Commit-Position: refs/heads/master@{#378600}

TBR=dpranke@chromium.org,thakis@chromium.org,atotic@google.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=
==========

[commit-bot: I haz the power, 2016-03-04 01:30:25]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-03-04 01:31:23]

Description was changed from

==========
Revert of add --gdb-index to linker (patchset #2 id:20001 of
https://codereview.chromium.org/1680943002/ )

Reason for revert:
We suspect this may be causing an increase in binary size on some chromeos PFQ
builders. Reverting to see if this is the cause.


Original issue's description:
> add --gdb-index to linker
> 
> gold linker has a flag to automatically generate gdb-index section
> inside shared libraries when linking.
> 
> Webkit single-file compile/linking time:
> 
> 16.31s without gdb-index
> 16.11s with gdb-index
> 
> gdb startup time
> 
> ~51s without gdb-index
> ~19s with gdb-index
> 
> BUG=
> 
> Committed: https://crrev.com/f68b7c07a30baac088b8eda055ba52835c04692c
> Cr-Commit-Position: refs/heads/master@{#378600}

TBR=dpranke@chromium.org,thakis@chromium.org,atotic@google.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=
==========

to

==========
Revert of add --gdb-index to linker (patchset #2 id:20001 of
https://codereview.chromium.org/1680943002/ )

Reason for revert:
We suspect this may be causing an increase in binary size on some chromeos PFQ
builders. Reverting to see if this is the cause.

Original issue's description:
> add --gdb-index to linker
>
> gold linker has a flag to automatically generate gdb-index section
> inside shared libraries when linking.
>
> Webkit single-file compile/linking time:
>
> 16.31s without gdb-index
> 16.11s with gdb-index
>
> gdb startup time
>
> ~51s without gdb-index
> ~19s with gdb-index
>
> BUG=
>
> Committed: https://crrev.com/f68b7c07a30baac088b8eda055ba52835c04692c
> Cr-Commit-Position: refs/heads/master@{#378600}

TBR=dpranke@chromium.org,thakis@chromium.org,atotic@google.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=

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

[commit-bot: I haz the power, 2016-03-04 01:31:24]

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

[stevenjb, 2016-03-04 23:02:18]

On 2016/03/04 01:31:24, commit-bot: I haz the power wrote:
> Patchset 1 (id:??) landed as
> https://crrev.com/b3521bc11841b49542d4b4c6a415167202ae151b
> Cr-Commit-Position: refs/heads/master@{#379165}

The revert did in fact fix the problem on Chrome OS, so let's not do this there
:)

FWIW, it only seemed to affect official chrome builders, not chromium os
builders.