On Wed, Nov 03, 2021 at 08:20:56PM -0700, Carlo Arenas wrote: > Agree it is OK as a minimal fix, but also AFAIK nothing is really > stuck either, so something as simple as : > > s/&ret/&async_die_counter/g > > Would make it as minimal, and less likely to trigger something else in > the future (I am surprised nothing warns about local variables being > used out of scope). It's in scope when we call the function. The potential for bugs only happens because we know pthread_setspecific() is going to hold on to it. So the compiler complaining would imply that it knows the semantics of the pthread function. -Peff
