Boost logo

Boost Users :

Subject: Re: [Boost-users] [boost] Boost.Fiber mini-review September 4-13
From: Hartmut Kaiser (hartmut.kaiser_at_[hidden])
Date: 2015-09-05 16:04:47


>> a) is safe as all threads sharing the same scheduler store the same
>> reference (fibers can be moved only inside that scheduler)
>> b) is safe as the runtime sets the reference to the fiber it is about to
>> run in TLS and resets it right after the fiber returned.
>
> but I was asking for the code snipped which accesses TLS variable - if all
> threads share the same scheduler why has it to be stored in TLS?
> a slight modification of my example above - replace
> retrn_ptr_of_scheduler_thread_lcoal_var() by return_ptr_to_active_fiber()
> I assume that as you mentioned in b) that the active fiber is stored in
> TLS - the exmaple code prints out the address of the current active fiber
> how does the code look like after compiler optimization?

I don't know. We have never ran into any problems related to this.

Regards Hartmut
---------------
http://boost-spirit.com
http://stellar.cct.lsu.edu


Boost-users list run by williamkempf at hotmail.com, kalb at libertysoft.com, bjorn.karlsson at readsoft.com, gregod at cs.rpi.edu, wekempf at cox.net