__declspec( thread )

Quote:

Originally Posted by TheCPUWizard

I would be interested in seeing the source of that reference. It is impossible to allocate and reference the space at process load time. There is no way of knowing if there are going to be 1 or 10000 threads running at a given time. The last time I actually looked at the disassembly the size of a TLS block was known, and dynamically allocated at thread creation, then all access was via an indexed offset

1) Again I question WHY the need. Your posted sample makes NO sense. If there is going to be one lock per thread, then the lock will NEVER get invoked!

The source of the reference is MSDN :D Actually, it is one of the links provided by you.
http://msdn2.microsoft.com/en-us/library/6yh4a9k1.aspx

1. There is one lock per producer thread. Each producer thread has two vectors where it posts the results. When a vector is full, it switches to the other vector.
There is also a consumer thread that checks all producer threads for vectors containing data. Producer/consumer must of course lock a vector to start producing/consuming.

I really appreciate your help. However, this discussion has gone a little out of control. If you don't have anything to say regarding how (the fastest form of) TLS is implemented, please do not post. If no one replies i will simply analyze the performance myself. Should not take long to find out whether it is slower than ordinary variable accesses.