A different, precise TLS garbage collector?

[Etienne via Digitalmars-d]

On Sunday, 16 November 2014 at 17:40:30 UTC, Sean Kelly wrote:
> On Sunday, 16 November 2014 at 17:38:54 UTC, Ola Fosheim 
> Grøstad wrote:
>>
>> But keep in mind that you also have to account for fibers that 
>> move between threads.
>
> Yes.  There are a lot of little "gotchas" with thread-local 
> allocation.

I can't even think of a situation when this would be necessary. 
It sounds like all I would need is to take the precise GC and 
store each instance in the thread data, I'll probably only need 
the rtinfo to see if it's shared during allocation to proxy 
towards malloc. Am I missing something?