On Thu, Feb 21, 2013 at 2:35 PM, Kai Tietz wrote:
> Well, I am right now playing with your test-case. I think we should
> approach it differently.
How?
> As by your code the TLS-region contains
> always one element.
"As by your code" - you mean as by the current tlssup.c
implementation? As lo
On Thu, Feb 21, 2013 at 1:47 PM, NightStrike wrote:
> On Tue, Feb 19, 2013 at 2:41 AM, David Nadlinger wrote:
>> Hi all,
>>
>> please find two patches to fix/improve TLS support in mingw-w64-crt attached.
>
> Do you have commit rights?
No.
>> Also, pleas
Hi Kai,
On Tue, Feb 19, 2013 at 7:27 PM, Kai Tietz wrote:
> - (ULONG_PTR) &_tls_start+1, (ULONG_PTR) &_tls_end,
> + (ULONG_PTR) &_tls_start, (ULONG_PTR) &_tls_end,
>
> looks to me wrong due we always have one pointer-size allocated in TLS.
>
> shouldn't be the required fix as the following here
Hi all,
please find two patches to fix/improve TLS support in mingw-w64-crt attached.
The first diff is an actual bug fix; it corrects the TLS start address
written to the TLS dictionary (_tls_used). It is used to determine the
size and initial contents of the TLS area for new threads. If it does
On 15 Jan 2013, at 20:24, Ruben Van Boxem wrote:
> As per request of Kai, I have built some small update packages for
> trunk
> MinGW-w64 dated 2013-01-15. It should contain changes useful to Clang
> developers and its TLS support.
Wow, that was quick – thanks a lot, this should make it much easi
