Revert of WTF::ThreadSpecific should use base::ThreadLocalStorage.

Revert of WTF::ThreadSpecific should use base::ThreadLocalStorage. (patchset #4 id:60001 of https://codereview.chromium.org/1849023002/ )

Reason for revert:
May have caused a bunch of perf regressions:
https://bugs.chromium.org/p/chromium/issues/detail?id=600271

Original issue's description:
> WTF::ThreadSpecific should use base::ThreadLocalStorage.
>
> Let's use the base abstraction to allocate the
> TLS. It's way less code.
>
> Committed: https://crrev.com/56641fdb889c6b5d27997465b622d7432c0ba0b8
> Cr-Commit-Position: refs/heads/master@{#384650}

TBR=danakj@chromium.org,haraken@chromium.org,yutak@chromium.org
NOTRY=true

Committed: https://crrev.com/4566bb7bf4a2c0d56474cd0b9e2f131df11d331d
Cr-Commit-Position: refs/heads/master@{#385013}

[esprehn, 2016-04-04 15:19:03]

Created Revert of WTF::ThreadSpecific should use base::ThreadLocalStorage.

[commit-bot: I haz the power, 2016-04-04 15:19:33]

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

[commit-bot: I haz the power, 2016-04-04 15:21:48]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-04-04 15:21:49]

Try jobs failed on following builders:
  ios_dbg_simulator_gn on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_dbg_simulator...)
  ios_dbg_simulator_ninja on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_dbg_simulator...)
  ios_rel_device_ninja on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_rel_device_ni...)

[esprehn, 2016-04-04 15:28:22]

Heh seems auto revert can't revet something that removes a file? :/

[haraken, 2016-04-04 15:43:26]

LGTM to revert.

[esprehn, 2016-04-04 19:27:01]

The CQ bit was checked by esprehn@chromium.org

[esprehn, 2016-04-04 19:27:02]

The patchset sent to the CQ was uploaded after l-g-t-m from haraken@chromium.org
Link to the patchset: https://codereview.chromium.org/1856793002/#ps170001
(title: " Manual revert")

[commit-bot: I haz the power, 2016-04-04 19:27:37]

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

[esprehn, 2016-04-04 21:32:00]

The CQ bit was unchecked by esprehn@chromium.org

[esprehn, 2016-04-04 21:32:09]

Description was changed from

==========
Revert of WTF::ThreadSpecific should use base::ThreadLocalStorage. (patchset #4
id:60001 of https://codereview.chromium.org/1849023002/ )

Reason for revert:
May have caused a bunch of perf regressions: 
https://bugs.chromium.org/p/chromium/issues/detail?id=600271

Original issue's description:
> WTF::ThreadSpecific should use base::ThreadLocalStorage.
> 
> Let's use the base abstraction to allocate the
> TLS. It's way less code.
> 
> Committed: https://crrev.com/56641fdb889c6b5d27997465b622d7432c0ba0b8
> Cr-Commit-Position: refs/heads/master@{#384650}

TBR=danakj@chromium.org,haraken@chromium.org,yutak@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
==========

to

==========
Revert of WTF::ThreadSpecific should use base::ThreadLocalStorage. (patchset #4
id:60001 of https://codereview.chromium.org/1849023002/ )

Reason for revert:
May have caused a bunch of perf regressions: 
https://bugs.chromium.org/p/chromium/issues/detail?id=600271

Original issue's description:
> WTF::ThreadSpecific should use base::ThreadLocalStorage.
> 
> Let's use the base abstraction to allocate the
> TLS. It's way less code.
> 
> Committed: https://crrev.com/56641fdb889c6b5d27997465b622d7432c0ba0b8
> Cr-Commit-Position: refs/heads/master@{#384650}

TBR=danakj@chromium.org,haraken@chromium.org,yutak@chromium.org
NOTRY=true
==========

[esprehn, 2016-04-04 21:32:12]

The CQ bit was checked by esprehn@chromium.org

[commit-bot: I haz the power, 2016-04-04 21:33:03]

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

[commit-bot: I haz the power, 2016-04-04 21:38:47]

Committed patchset #2 (id:170001)

[commit-bot: I haz the power, 2016-04-04 21:40:04]

Description was changed from

==========
Revert of WTF::ThreadSpecific should use base::ThreadLocalStorage. (patchset #4
id:60001 of https://codereview.chromium.org/1849023002/ )

Reason for revert:
May have caused a bunch of perf regressions: 
https://bugs.chromium.org/p/chromium/issues/detail?id=600271

Original issue's description:
> WTF::ThreadSpecific should use base::ThreadLocalStorage.
> 
> Let's use the base abstraction to allocate the
> TLS. It's way less code.
> 
> Committed: https://crrev.com/56641fdb889c6b5d27997465b622d7432c0ba0b8
> Cr-Commit-Position: refs/heads/master@{#384650}

TBR=danakj@chromium.org,haraken@chromium.org,yutak@chromium.org
NOTRY=true
==========

to

==========
Revert of WTF::ThreadSpecific should use base::ThreadLocalStorage. (patchset #4
id:60001 of https://codereview.chromium.org/1849023002/ )

Reason for revert:
May have caused a bunch of perf regressions:
https://bugs.chromium.org/p/chromium/issues/detail?id=600271

Original issue's description:
> WTF::ThreadSpecific should use base::ThreadLocalStorage.
>
> Let's use the base abstraction to allocate the
> TLS. It's way less code.
>
> Committed: https://crrev.com/56641fdb889c6b5d27997465b622d7432c0ba0b8
> Cr-Commit-Position: refs/heads/master@{#384650}

TBR=danakj@chromium.org,haraken@chromium.org,yutak@chromium.org
NOTRY=true

Committed: https://crrev.com/4566bb7bf4a2c0d56474cd0b9e2f131df11d331d
Cr-Commit-Position: refs/heads/master@{#385013}
==========

[commit-bot: I haz the power, 2016-04-04 21:40:05]

Patchset 2 (id:??) landed as
https://crrev.com/4566bb7bf4a2c0d56474cd0b9e2f131df11d331d
Cr-Commit-Position: refs/heads/master@{#385013}

[esprehn, 2016-04-04 23:48:03]

Woops forgot BUG=,

See https://bugs.chromium.org/p/chromium/issues/detail?id=600271