Revert of Clang update.py: enable debug info for ToT builds

Revert of Clang update.py: enable debug info for ToT builds (patchset #1 id:1 of https://codereview.chromium.org/2213743002/ )

Reason for revert:
Speculative. clang binaries started failing without any message (e.g. https://build.chromium.org/p/chromium.fyi/builders/CrWinAsanCov/builds/2740/steps/compile/logs/stdio). I don't see how this change could cause that, but it's in the blame list of each of the win bots where this fails, non-win bots are fine, and this is the only thing I see that is vaguely related.

Original issue's description:
> Clang update.py: enable debug info for ToT builds
>
> This should give us better stack traces when Clang crashes, which is
> useful when doing ToT builds, whose purpose is to catch Clang regressions
> early.
>
> BUG=none
>
> Committed: https://crrev.com/c58e45deb3bbb26184bb6b034b785fbfec89668e
> Cr-Commit-Position: refs/heads/master@{#409802}

TBR=rnk@chromium.org,hans@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=none

Committed: https://crrev.com/949ce560edea778357f6df5441b68d66144048f8
Cr-Commit-Position: refs/heads/master@{#409893}

[Nico, 2016-08-04 20:43:16]

The CQ bit was checked by thakis@chromium.org

[Nico, 2016-08-04 20:43:17]

Created Revert of Clang update.py: enable debug info for ToT builds

[commit-bot: I haz the power, 2016-08-04 20:43:37]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-04 20:44:26]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-08-04 20:45:55]

Description was changed from

==========
Revert of Clang update.py: enable debug info for ToT builds (patchset #1 id:1 of
https://codereview.chromium.org/2213743002/ )

Reason for revert:
Speculative. clang binaries started failing without any message (e.g.
https://build.chromium.org/p/chromium.fyi/builders/CrWinAsanCov/builds/2740/s...).
I don't see how this change could cause that, but it's in the blame list of each
of the win bots where this fails, non-win bots are fine, and this is the only
thing I see that is vaguely related.

Original issue's description:
> Clang update.py: enable debug info for ToT builds
> 
> This should give us better stack traces when Clang crashes, which is
> useful when doing ToT builds, whose purpose is to catch Clang regressions
> early.
> 
> BUG=none
> 
> Committed: https://crrev.com/c58e45deb3bbb26184bb6b034b785fbfec89668e
> Cr-Commit-Position: refs/heads/master@{#409802}

TBR=rnk@chromium.org,hans@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=none
==========

to

==========
Revert of Clang update.py: enable debug info for ToT builds (patchset #1 id:1 of
https://codereview.chromium.org/2213743002/ )

Reason for revert:
Speculative. clang binaries started failing without any message (e.g.
https://build.chromium.org/p/chromium.fyi/builders/CrWinAsanCov/builds/2740/s...).
I don't see how this change could cause that, but it's in the blame list of each
of the win bots where this fails, non-win bots are fine, and this is the only
thing I see that is vaguely related.

Original issue's description:
> Clang update.py: enable debug info for ToT builds
>
> This should give us better stack traces when Clang crashes, which is
> useful when doing ToT builds, whose purpose is to catch Clang regressions
> early.
>
> BUG=none
>
> Committed: https://crrev.com/c58e45deb3bbb26184bb6b034b785fbfec89668e
> Cr-Commit-Position: refs/heads/master@{#409802}

TBR=rnk@chromium.org,hans@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=none

Committed: https://crrev.com/949ce560edea778357f6df5441b68d66144048f8
Cr-Commit-Position: refs/heads/master@{#409893}
==========

[commit-bot: I haz the power, 2016-08-04 20:45:56]

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

[Nico, 2016-08-04 22:01:58]

Compiles work again now. Begin of breakage and end of breakage correlate exactly
with landing and reverting this CL, so it's likely it is indeed the cause. No
idea why though.