[bug #34832] enable tls variable in windows code for newish gcc

[Paul D. Smith]

Follow-up Comment #7, bug #34832 (project make):

That function is used a lot in job.c, main.c, commands.c.

But I agree with Eli: what's the need for having this variable be thread-safe
in the first place?  GNU make is not multithreaded (there would be a LOT of
work needed to make that possible).  Is there some attribute of the W32 API,
or the way this variable is used, that requires it to be thread-local?

Maybe the right thing to do is remove the existing thread safety stuff, not
enhancing it for new compilers...?  But I don't know enough about Windows to
say.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?34832>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/