> 0) complexifies comparison of thread IDs without obvious benefits, and
The reverse argument is also true: using IDs would complexify everything else
with the only benefit of simplifying the equal primitive.
> 1) does not work reliably because handles can be duplicated, and
That's pure FUD.
>
在 2019/7/29 22:43, JonY 写道:
>
> Any updates?
>
No. I am still under the impression that using thread handles as
`std::thread::id`s:
0) complexifies comparison of thread IDs without obvious benefits, and
1) does not work reliably because handles can be duplicated, and
2) makes `__gthread_self()`
On 7/3/19 12:55 PM, Liu Hao wrote:
> 在 2019/7/2 下午8:27, Jonathan Wakely 写道:
>>
>> What do you mean by "unclosed thread"? If I read it correctly, the MSDN
>> page
>> refers to closing a handle (which makes sense), not closing a thread.
>>
>
> Yes, it meant a thread which has terminated but not dele
On 02/07/19 12:15 +0200, Jacek Caban wrote:
On 02/07/2019 12:12, Jacek Caban wrote:
On 02/07/2019 11:57, Liu Hao wrote:
在 2019/7/2 下午5:19, Eric Botcazou 写道:
It seems inappropriate to use handles as thread identifiers
(as handles
imply resource ownership and are not unique identifiers);
thre
> It seems inappropriate to use handles as thread identifiers (as handles
> imply resource ownership and are not unique identifiers); thread IDs (as
> `DWORD` or `unsigned long`) would be a better alternative.
This was considered but ultimately rejected, as you can do nothing with a
thread Id, i.
On 02/07/19 20:14 +0800, Liu Hao wrote:
在 2019/7/2 下午8:00, Jonathan Wakely 写道:
The C++ standard says:
"The library may reuse the value of a thread::id of a terminated
thread that can no longer be joined."
So that's not a reason to use a handle.
According to MSDN [1] a thread ID is valid 'unt
在 2019/7/2 下午8:27, Jonathan Wakely 写道:
>
> What do you mean by "unclosed thread"? If I read it correctly, the MSDN
> page
> refers to closing a handle (which makes sense), not closing a thread.
>
Yes, it meant a thread which has terminated but not deleted due to some
handles left open.
>> This
On 02.07.2019 14:58, Jacek Caban wrote:
> On 7/2/19 1:35 PM, LRN wrote:
>> On 02.07.2019 13:42, Jacek Caban wrote:
>>> On 02/07/2019 12:38, LRN wrote:
On 02.07.2019 13:15, Jacek Caban wrote:
> On 02/07/2019 12:12, Jacek Caban wrote:
>> On 02/07/2019 11:57, Liu Hao wrote:
>>
>>>
On 02.07.2019 15:14, Liu Hao wrote:
> 在 2019/7/2 下午8:00, Jonathan Wakely 写道:
>> The C++ standard says:
>>
>> "The library may reuse the value of a thread::id of a terminated
>> thread that can no longer be joined."
>>
>> So that's not a reason to use a handle.
>
> According to MSDN [1] a thread ID
在 2019/7/2 下午8:00, Jonathan Wakely 写道:
> The C++ standard says:
>
> "The library may reuse the value of a thread::id of a terminated
> thread that can no longer be joined."
>
> So that's not a reason to use a handle.
According to MSDN [1] a thread ID is valid 'until the thread has been
terminate
On 7/2/19 1:35 PM, LRN wrote:
On 02.07.2019 13:42, Jacek Caban wrote:
On 02/07/2019 12:38, LRN wrote:
On 02.07.2019 13:15, Jacek Caban wrote:
On 02/07/2019 12:12, Jacek Caban wrote:
On 02/07/2019 11:57, Liu Hao wrote:
在 2019/7/2 下午5:19, Eric Botcazou 写道:
It seems inappropriate to use handl
On 02.07.2019 13:42, Jacek Caban wrote:
>
> On 02/07/2019 12:38, LRN wrote:
>> On 02.07.2019 13:15, Jacek Caban wrote:
>>> On 02/07/2019 12:12, Jacek Caban wrote:
On 02/07/2019 11:57, Liu Hao wrote:
> 在 2019/7/2 下午5:19, Eric Botcazou 写道:
>>> It seems inappropriate to use handles
On 02/07/2019 12:38, LRN wrote:
On 02.07.2019 13:15, Jacek Caban wrote:
On 02/07/2019 12:12, Jacek Caban wrote:
On 02/07/2019 11:57, Liu Hao wrote:
在 2019/7/2 下午5:19, Eric Botcazou 写道:
It seems inappropriate to use handles as thread identifiers (as
handles
imply resource ownership and are n
On 02.07.2019 13:15, Jacek Caban wrote:
>
> On 02/07/2019 12:12, Jacek Caban wrote:
>> On 02/07/2019 11:57, Liu Hao wrote:
>>
>>> 在 2019/7/2 下午5:19, Eric Botcazou 写道:
> It seems inappropriate to use handles as thread identifiers (as
> handles
> imply resource ownership and are not uni
On 02/07/2019 12:12, Jacek Caban wrote:
On 02/07/2019 11:57, Liu Hao wrote:
在 2019/7/2 下午5:19, Eric Botcazou 写道:
It seems inappropriate to use handles as thread identifiers (as
handles
imply resource ownership and are not unique identifiers); thread
IDs (as
`DWORD` or `unsigned long`) would
On 02/07/2019 11:57, Liu Hao wrote:
在 2019/7/2 下午5:19, Eric Botcazou 写道:
It seems inappropriate to use handles as thread identifiers (as handles
imply resource ownership and are not unique identifiers); thread IDs (as
`DWORD` or `unsigned long`) would be a better alternative.
This was consider
在 2019/7/2 下午5:19, Eric Botcazou 写道:
>> It seems inappropriate to use handles as thread identifiers (as handles
>> imply resource ownership and are not unique identifiers); thread IDs (as
>> `DWORD` or `unsigned long`) would be a better alternative.
>
> This was considered but ultimately rejected,
On Fri, Jun 28, 2019 at 7:17 PM Ruben Van Boxem
wrote:
>
>
> I'm interested in seeing real-world benchmarks when using this code!
that is something i would really like too
Vincent Torri
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourcef
在 2019/6/29 上午12:10, Jacek Caban 写道:
>
> You don't really need to store the whole __gthr_win32_thr_desc in TLS.
> If you stored just the handle, this wouldn't need a destructor.
>
>
The handle to be stored in the TLS ('the Handle' for short hereinafter)
should be a real handle, so there are a f
This is awesome!
Although winpthreads was a nice in-between solution for this (and it still
is a good solution for those who want a pthreads library on Windows), this
is what everyone (using C++ and/or OpenMP, heck, even C11 thread support)
needs of course.
I'm interested in seeing real-world ben
Hi Eric,
On 6/28/19 3:42 PM, NightStrike wrote:
FYI, Eric posted this today to the GCC patches list. This may be of
great interest to many who would prefer native threads instead of the
winpthreads posix style interface.
Great work, Eric! I look forward to trying this out!
-- Forward
FYI, Eric posted this today to the GCC patches list. This may be of
great interest to many who would prefer native threads instead of the
winpthreads posix style interface.
Great work, Eric! I look forward to trying this out!
-- Forwarded message -
From: Eric Botcazou
Date: Fri
22 matches
Mail list logo
