From 475c85f4626d34629f3eba870f70b00118201c7e Mon Sep 17 00:00:00 2001 From: Martin Kinkelin Date: Wed, 11 Mar 2020 21:40:35 +0100 Subject: [PATCH] rt.sections_android: Don't bother excluding static TLS data from GC scanning As it apparently doesn't always end up at the start of the data segment, e.g., with the gold linker, see https://github.com/ldc-developers/ldc/issues/3350#issuecomment-597735906. It should be rather small in most cases, especially in comparison to the ranges on the heap, so just don't bother. --- src/rt/sections_android.d | 8 -------- 1 file changed, 8 deletions(-) diff --git a/src/rt/sections_android.d b/src/rt/sections_android.d index c5fa3882ac..8eed012081 100644 --- a/src/rt/sections_android.d +++ b/src/rt/sections_android.d @@ -95,14 +95,6 @@ void initSections() nothrow @nogc void* end = start + phdr.p_memsz; debug(PRINTF) printf("data segment: %p - %p\n", start, end); - // exclude static TLS range - if (_staticTLSRange.length) - { - safeAssert(start == _staticTLSRange.ptr, - "static TLS range expected to be at start of data segment"); - start += _staticTLSRange.length; - } - // pointer-align up enum mask = size_t.sizeof - 1; start = cast(void*) ((cast(size_t)start + mask) & ~mask);