This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Fall back to a link test for TLS in target libraries

From: David Daney <ddaney at avtrex dot com>
To: Daniel Jacobowitz <drow at false dot org>
Cc: gcc-patches at gcc dot gnu dot org
Date: Wed, 08 Nov 2006 13:19:16 -0800
Subject: Re: Fall back to a link test for TLS in target libraries
References: <20061108210943.GB7234@nevyn.them.org>

Daniel Jacobowitz wrote:

Any thoughts on this patch?  I know that link tests can be troublesome
in target libraries, but I'm not sure what else to do.  I recently
tried to build GCC on an ARM LinuxThreads-only system which did not
provide __tls_get_addr in libc.  So the compile test passed, but the
link test would have failed, and prevented building a broken library
(libjava in this case; the first program to fail to link was gij).

I guess one extension of it would be to check the flag set by
GCC_NO_EXECUTABLES.

I am all for it.

The main reason I added the --[enable|disable]-tls option to configure was because I was too lazy to write the link test.

FWIW, The exact same problem on mipsel-linux was the driving factor for the --disable-tls hack.

David Daney

References:
- Fall back to a link test for TLS in target libraries
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]