dim 992b29a96b Pull in r353299 from upstream lld trunk (by George Rimar):
Recommit r353293 "[LLD][ELF] - Set DF_STATIC_TLS flag for i386 target."

  With the following changes:
  1) Compilation fix:
  std::atomic<bool> HasStaticTlsModel = false; ->
  std::atomic<bool> HasStaticTlsModel{false};

  2) Adjusted the comment in code.

  Initial commit message:

  DF_STATIC_TLS flag indicates that the shared object or executable
  contains code using a static thread-local storage scheme.

  Patch checks if IE/LE relocations were used to check if the code uses
  a static model. If so it sets the DF_STATIC_TLS flag.

  Differential revision: https://reviews.llvm.org/D57749

Pull in r353378 from upstream lld trunk (by George Rimar):

  [LLD][ELF] - Set DF_STATIC_TLS flag for X64 target

  This is the same as D57749, but for x64 target.

  "ELF Handling For Thread-Local Storage" p41 says
  (https://www.akkadia.org/drepper/tls.pdf):
  R_X86_64_GOTTPOFF relocation is used for IE TLS models.
  Hence if linker sees this relocation we should add DF_STATIC_TLS flag.

  Differential revision: https://reviews.llvm.org/D57821

This adds support to lld for the DF_STATIC_TLS flag in shared objects,
which signals to the dynamic linker that the shared object requires
static thread local storage.

See also:	https://reviews.freebsd.org/D19072
MFC after:	1 week
2019-02-21 18:41:41 +00:00
..
2018-12-23 01:05:52 +00:00
2018-10-20 20:49:46 +00:00
2018-09-19 06:42:05 +00:00
2018-11-04 18:24:11 +00:00
2018-08-08 01:33:36 +00:00
2018-10-19 00:37:47 +00:00
2018-02-19 05:10:22 +00:00
2019-02-13 07:37:33 +00:00
2018-05-31 09:11:21 +00:00
2018-08-14 18:58:01 +00:00
2018-08-21 02:38:07 +00:00
2018-11-26 15:33:55 +00:00
2018-01-28 03:16:54 +00:00
2018-12-18 01:12:30 +00:00
2018-05-08 04:52:52 +00:00
2018-09-19 07:01:22 +00:00
2018-12-31 07:57:37 +00:00
2018-12-09 06:45:49 +00:00