Use 'local-exec' for threadlocal_heap_ in tcmalloc.

third_party/tcmalloc/chromium/src/thread_cache.cc

 // Copyright (c) 2008, Google Inc.
 // All rights reserved.
 //
 // Redistribution and use in source and binary forms, with or without
 // modification, are permitted provided that the following conditions are
 // met:
 //
 //     * Redistributions of source code must retain the above copyright
 // notice, this list of conditions and the following disclaimer.
 //     * Redistributions in binary form must reproduce the above
@@ skipping 49 matching lines @@
 ssize_t ThreadCache::unclaimed_cache_space_ = kDefaultOverallThreadCacheSize;
 PageHeapAllocator<ThreadCache> threadcache_allocator;
 ThreadCache* ThreadCache::thread_heaps_ = NULL;
 int ThreadCache::thread_heap_count_ = 0;
 ThreadCache* ThreadCache::next_memory_steal_ = NULL;
 #ifdef HAVE_TLS
 __thread ThreadCache* ThreadCache::threadlocal_heap_
 // See comments in thread_cache.h about this. Bug here:
 // http://code.google.com/p/chromium/issues/detail?id=124489
 #if defined(HAVE___ATTRIBUTE__) && !defined(PGO_GENERATE)
+// If we are not using component build, we can further optimize it.
+#if !defined(COMPONENT_BUILD)
+   __attribute__ ((tls_model ("local-exec")))
+#else
    __attribute__ ((tls_model ("initial-exec")))
+#endif
 # endif
    ;
 #endif
 bool ThreadCache::tsd_inited_ = false;
 pthread_key_t ThreadCache::heap_key_;
 
 #if defined(HAVE_TLS)
 bool kernel_supports_tls = false;      // be conservative
 # if defined(_WIN32)    // windows has supported TLS since winnt, I think.
     void CheckIfKernelSupportsTLS() {
@@ skipping 424 matching lines @@
 void ThreadCache::set_overall_thread_cache_size(size_t new_size) {
   // Clip the value to a reasonable range
   if (new_size < kMinThreadCacheSize) new_size = kMinThreadCacheSize;
   if (new_size > (1<<30)) new_size = (1<<30);     // Limit to 1GB
   overall_thread_cache_size_ = new_size;
 
   RecomputePerThreadCacheSize();
 }
 
 }  // namespace tcmalloc