Hi people,
I'm porting a project, which uses TLS in performance-critical code. I
currently use mingw-w64 (i686-4.9.1-posix-dwarf-rt_v3-rev0) on Win 7 SP1
Professional x86 and libgcc_s_dw2-1!__emutls_get_address is one of the
hotspots in the product. Thus the question: why mingw-w64
2014-08-13 10:34 GMT+02:00 Slava viatcheslav.sysolt...@h-d-gmbh.de:
Hi people,
I'm porting a project, which uses TLS in performance-critical code. I
currently use mingw-w64 (i686-4.9.1-posix-dwarf-rt_v3-rev0) on Win 7 SP1
Professional x86 and libgcc_s_dw2-1!__emutls_get_address is one of the
-w64-public
抄送：
主题：[Mingw-w64-public] emutls?
Hi people,
I'm porting a project, which uses TLS in performance-critical code. I
currently use mingw-w64 (i686-4.9.1-posix-dwarf-rt_v3-rev0) on Win 7 SP1
Professional x86 and libgcc_s_dw2-1!__emutls_get_address is one of the
hotspots in the product
-
发件人：Slava viatcheslav.sysolt...@h-d-gmbh.de
发送日期：2014-08-13 16:34
收件人：mingw-w64-public
抄送：
主题：[Mingw-w64-public] emutls?
Hi people,
I'm porting a project, which uses TLS in performance-critical code. I
currently use mingw-w64 (i686-4.9.1-posix-dwarf-rt_v3-rev0) on Win
On Wed, 13 Aug 2014 10:54:32 +0200, Kai Tietz
ktiet...@googlemail.com wrote:
I am aware that emultls is pretty slow in comparison to OS-variant of
TLS. I have prepared already implementation for it a bit,
nevertheless I don't find enough time to push work on it. AFAIR is
new D FE
