You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The notion of C11 thread-local variables seems to map onto pthread_getspecific & pthread_setspecific. So when adding support for C11, support for this should be added to.
The text was updated successfully, but these errors were encountered:
Besides C11's thread-local specifier there is also GCC's __thread that we found with @vesalvojdani in silver searcher. It should be very easy to just ignore races on thread-local things.
sim642
changed the title
Support for C11 thread-local variables / pthread_getspecific & pthread_setspecific
Support for thread-local variables / pthread_getspecific & pthread_setspecificNov 23, 2022
I think the good first issue applies mostly to not reporting races for these variables, the support to privatize the values is a bit trickier - one has to think a bit what happens when thread ids are non-unique (it would seem like that should also work, but some thought is needed here).
#1071 handles the race checking of __thread, but there's still C11's _Thread_local for which the same could apply. It probably requires changes in CIL as well: goblint/cil#13.
The notion of C11 thread-local variables seems to map onto
pthread_getspecific
&pthread_setspecific
. So when adding support for C11, support for this should be added to.The text was updated successfully, but these errors were encountered: