https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105710
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=52268,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=53504
--- Comment #7 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Sergey Fedorov from comment #4)
> (In reply to Andrew Pinski from comment #3)
> > (In reply to Sergey Fedorov from comment #2)
> > > (In reply to Andrew Pinski from comment #1)
> > > > >TLS enabled
> > > >
> > > > TLS support for powerpc darwin was never added.
> > >
> > > Iain writes that emulated TLS is supported on all Darwin versions starting
> > > from 10.5:
> > > https://github.com/ruby/ruby/pull/5927?notification_referrer_id=NT_kwDOBXwLlrMzNjYyMzQ0NjYzOjkyMDE1NTEw#issuecomment-1133843490
> >
> > That is enabled by default though --enable-tls tries to enable native TLS
> > support.
>
> From what I understand, native TLS does not exist with gcc, at least for
> Darwin.
That's bug 52268, for reference.
(In reply to Iain Sandoe from comment #5)
> Correct (even if it did exist it would only be for 10.7+) so --enable-tls is
> a configuration error.
>
> (as I have said several times, the idea of configure is to choose the
> correct settings for the target _automatically_ - extra config options
> should only be added if there is a very good reason and you know exactly
> what they do).
Well we could at least make the error happen earlier rather than letting it
turn into an ICE. I think making the configure script smarter about whether TLS
works or not could be worthwhile; see bug 53504
