Excellent - thank you so much for accepting our proposal.
Xerxes also confirmed that the fix solves the problem in the processing-2.0a5
build
using Mesa/Ubuntu.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchp
Thank you Chris for responding and describing the history and motivation
of the patch.
Regarding visibility, I read in the same tls paper, that global exposes the tls
field[s]
to the 'calling' library and executables as well, where the other models don't.
Hence I would be able to access them dir
Allow me to start a discussion about the motivation of the tls-global path
113_fix_tls.diff
and pls correct me if I am wrong ... ofc.
[1] tls-global implies that all the tls fields are directly exposed to the
other library or executable loading the
tls-global exposed library.
[1.1] This is IMH
Allow me to copy my analysis of this bug here
from https://jogamp.org/bugzilla/show_bug.cgi?id=566#c13
This bug affects all Mesa8 w/ the tls_model("global-dynamic") patch
enabled!
+++
Analysis of patch 113_fix_tls.diff and it's freezing impact:
+++
extern __thread void *u_current_user
-__a
4 matches
Mail list logo