Displaying 10 results from an estimated 10 matches for "win32thread".
Did you mean:
win32threads
2014 Sep 26
3
[LLVMdev] [lldb-dev] RFC: LLVM should require a working C++11 <thread>, <mutex>, and <atomic>
...is less that I remember seeing last year (something got optimized?),
but still...
Vadim
On Fri, Sep 26, 2014 at 3:29 AM, Yaron Keren <yaron.keren at gmail.com> wrote:
> Yes, of course.
>
> I refer to the significant slowdown of Rust compiler when compiled with
> -pthreads vs -win32threads flavor.
> If Rust can be compiled without <mutex> and <thread> on win32threads, why
> should it slow down on pthreads?
> Isn't the only difference betwen the win32threads and pthreads is the
> addition of pthreads, <mutex> and <thread>?
>
> Yaron
>...
2014 Sep 26
2
[LLVMdev] [lldb-dev] RFC: LLVM should require a working C++11 <thread>, <mutex>, and <atomic>
...way, does the -win32 version have any feature that
> -pthreads vesion do not have?
>
> Yaron
>
>
> 2014-09-25 9:52 GMT+03:00 Vadim Chugunov <vadimcn at gmail.com>:
>
>> Hi,
>> I think I can at least answer why the Rust project prefers to use
>> mingw-w64-win32threads:
>> 1. It does not inject dependency on libwinpthread.dll, which is nice.
>> 2. Those who tried building LLVM with mingw-w64-pthreads, had reported
>> significant slowdown of the resulting Rust compiler (as compared to one
>> linked to LLVM compiled with the win32threads fl...
2014 Sep 25
2
[LLVMdev] [lldb-dev] RFC: LLVM should require a working C++11 <thread>, <mutex>, and <atomic>
Hi,
I think I can at least answer why the Rust project prefers to use
mingw-w64-win32threads:
1. It does not inject dependency on libwinpthread.dll, which is nice.
2. Those who tried building LLVM with mingw-w64-pthreads, had reported
significant slowdown of the resulting Rust compiler (as compared to one
linked to LLVM compiled with the win32threads flavor). Profiling seemed
to point t...
2014 Sep 24
14
[LLVMdev] RFC: LLVM should require a working C++11 <thread>, <mutex>, and <atomic>
AKA: MinGW + win32threads is holding LLVM (and all of its subprojects)
back. We need to stop supporting this host platform.
I'm aware of essentially 2 reasonably important use cases for supporting
MinGW + win32threads:
1) Sane host toolchain on Windows that doesn't require downloading MSVC.
(I'm dubious about...
2014 Sep 24
2
[LLVMdev] RFC: LLVM should require a working C++11 <thread>, <mutex>, and <atomic>
...ing List; clang-dev Developers;
> lldb-dev at cs.uiuc.edu; Chris Bieneman; Reid Kleckner; David Majnemer; Alex
> Rosenberg; Zachary Turner
> *Subject:* [LLVMdev] RFC: LLVM should require a working C++11 <thread>,
> <mutex>, and <atomic>
>
>
>
> AKA: MinGW + win32threads is holding LLVM (and all of its subprojects)
> back. We need to stop supporting this host platform.
>
>
>
> I'm aware of essentially 2 reasonably important use cases for supporting
> MinGW + win32threads:
>
>
>
> 1) Sane host toolchain on Windows that doesn't...
2015 Jul 16
2
[LLVMdev] [lldb-dev] [3.7 Release] We have branched
...DE_SCRIPTS
> -DPERL_IMPLICIT_CONTEXT -DPERL_IMPLICIT_SYS -TP -EHsc -Foperllib.obj
> perllib.c
> clang-cl.exe: warning: argument unused during compilation: '-GL'
> In file included from perllib.c:10:
> In file included from ..\lib\CORE\perl.h:3060:
> In file included from .\win32thread.h:4:
> ./win32.h(284,25) : error: 'selectany' can only be applied to data items
> with external linkage
>
That line is:
extern const __declspec(selectany) union { unsigned __int64 __q; double
__d; } __PL_nan_u = { 0x7FF8000000000000UI64 };
If it's written like so, clang-cl a...
2015 Jul 24
0
[LLVMdev] [lldb-dev] [3.7 Release] We have branched
...RL_IMPLICIT_CONTEXT -DPERL_IMPLICIT_SYS -TP -EHsc -Foperllib.obj
>> perllib.c
>> clang-cl.exe: warning: argument unused during compilation: '-GL'
>> In file included from perllib.c:10:
>> In file included from ..\lib\CORE\perl.h:3060:
>> In file included from .\win32thread.h:4:
>> ./win32.h(284,25) : error: 'selectany' can only be applied to data items
>> with external linkage
>>
>
> That line is:
> extern const __declspec(selectany) union { unsigned __int64 __q; double
> __d; } __PL_nan_u = { 0x7FF8000000000000UI64 };
>
>...
2015 Jul 24
2
[LLVMdev] [lldb-dev] [3.7 Release] We have branched
...-DPERL_IMPLICIT_SYS -TP -EHsc -Foperllib.obj
>>> perllib.c
>>> clang-cl.exe: warning: argument unused during compilation: '-GL'
>>> In file included from perllib.c:10:
>>> In file included from ..\lib\CORE\perl.h:3060:
>>> In file included from .\win32thread.h:4:
>>> ./win32.h(284,25) : error: 'selectany' can only be applied to data
>>> items with external linkage
>>>
>>
>> That line is:
>> extern const __declspec(selectany) union { unsigned __int64 __q; double
>> __d; } __PL_nan_u = { 0x7FF80...
2014 Sep 29
2
[LLVMdev] LLVM Weekly - #39, Sep 29th 2014
...benchmark in SPEC CPU2006 relies on it returning a NaN apparently.
* Chandler Carruth has posted an RFC proposing that [LLVM should require a
working C++11 thread, mutex, and
atomic](http://article.gmane.org/gmane.comp.compilers.llvm.devel/77148) with
the intention being that support for MinGW and win32threads is dropped.
Switching to MinGW-win64 seems like a feasible path forwards.
* Wondering how to use noalias and alias.scope metadata notations? Hal Finkel
[has the
answer](http://article.gmane.org/gmane.comp.compilers.llvm.devel/77174) for
you.
* Should the LLVM project standardise on a [commit mes...
2015 Jul 15
10
[LLVMdev] [3.7 Release] We have branched
Hi all,
The 3.7 release branch was created from trunk at r242221 today (around
10:40 pm UTC).
Branch policy:
- Any doc changes can go in. Updates to the release notes are highly
encouraged, and should be committed directly to the branch.
- All other patches should be approved by the release manager (me) and
the appropriate code owner. To get a change merged, commit it to
trunk, and then reply