On 11/15/13 10:00 AM, Daniel Micay wrote:
If you pin the task and other tasks aren't allowed to use the thread, it would work. The library would have to do this in all the entry points to provide safety and there would have to be no way of unpinning a task in safe code or at least a separate mandatory pinning concept.
Mandatory pinning for safety is needed anyway, for example for OpenGL.
The issue is that the thread-local data is used by outputting accesses through an x86 segment register (and similarly on other architectures) so 1:1 vs. M:N would become a compile-time choice.
I'm fine with that. Patrick _______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
