No threadsafe statics.

No threadsafe statics.

Chrome disables these for speed and code size, so we need
to disable them to make sure our code is safe when used
this way.

    int foo() {
        static int32_t atomic_thing;
        return sk_atomic_inc(&atomic_thing);
    }

is not safe in Chrome.  Making the static global is:

    static int32_t atomic_thing;
    int foo() {
        return sk_atomic_inc(&atomic_thing);
    }

BUG=skia:

Committed: https://skia.googlesource.com/skia/+/cad5d3e264535c919b80e1e2a85407307961f221

[mtklein, 2014-10-13 19:05:30]

mtklein@google.com changed reviewers:
+ bungeman@google.com, mtklein@google.com

[bungeman-skia, 2014-10-13 19:07:56]

lgtm

[mtklein, 2014-10-13 19:08:03]

The CQ bit was checked by mtklein@google.com

[commit-bot: I haz the power, 2014-10-13 19:09:12]

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

[commit-bot: I haz the power, 2014-10-13 19:53:31]

Committed patchset #1 (id:1) as cad5d3e264535c919b80e1e2a85407307961f221

[mtklein, 2014-10-13 21:49:33]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/649343003/ by mtklein@google.com.

The reason for reverting is: Want to think about how to do this only to skialib
and not to tools (gms, tests, etc.).