- User Since
- Jan 9 2018, 8:54 AM (106 w, 2 d)
Jul 24 2019
Jul 17 2019
May 15 2019
May 13 2019
i think this should be fixed in the tools/runtimes that assume fixed tls offset abi that conflict with the elf tls abi.
i think glibc is right (comes up with a tlsoffset%p_align == p_vaddr%p_align for the module) and musl and other implementations are wrong (they may not get the tlsoffset right in this case: it seems musl always computes tlsoffset%p_align==0 on tls variant 1 targets).
Jan 26 2018
Jan 12 2018
Jan 11 2018
also note that there is less than 3 weeks until glibc-2.27 is released, if the headers need a fix for clang then say so quickly
if clang wants to provide _Float128 then the f128 constant suffix (specified by TS18661-3) and builtin_inff128, builtin_nanf128, builtin_nansf128, builtin_huge_valf128 (gcc builtins required by math.h) need to be supported too.