https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80881
--- Comment #88 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- > Eric, I've just come to realize that the configure check might not be > needed, because the intention is to only allow native TLS on Windows when > --enable-tls is forcefully enabled, similar to win32 thread model in > libstdc++ requiring --enable-libstdcxx-threads before it is enabled > properly. This in effect restricts native TLS only to vendors who know what > they're doing, and they would already know that a specific binutils version > without the linker bug is required. By default, the lack of a configure > check for TLS achieves just that, and --enable-tls bypasses the check > anyway. Anyone have any objections if I back out the (Admittedly also poorly > written) check from configure? Yes, in my opinion the check is an extra safety net and should be kept now that it has been written. TLS binutils support is really bleeding edge.
