Hey John
I think you are confusing Discord and Discourse.
Jeroen
On Thu, Jan 20, 2022, 15:51 via cfe-users wrote:
> This seems like a mistake. Discord is pretty good for tight communities
> where everyone wants to know about everything that’s going on, and don’t
> need to refer back to old inf
Hey Kyle,
This is a bug in your code, if you have a context switch after the creation
of the thread on an overloaded system, the close of the pipe can be closed
while writing or even before it.
Timing ain't a good way to synchronize threads. TSan is correct in flagging
this occurrence.
On Fri,
Hey Mario,
I logged a bug for this a long time ago:
https://bugs.llvm.org/show_bug.cgi?id=25319
>From what I can see, this still ain't solved.
It makes sense to register you onto that one.
On Thu, Jan 30, 2020, 19:02 Mario Charest via cfe-users <
cfe-users@lists.llvm.org> wrote:
> Hello,
>
> Fi
Hi all,
I know already about the Tread Safety Analysis annotations (see
http://clang.llvm.org/docs/ThreadSafetyAnalysis.html).
I love the idea and would like to use it one day in real production code.
However, right now, it seems you should always use macros for indicating
this code. These macros
Hi all
We are looking at a large project that has been written only with the MSVC
compiler.
I've already tried to compile this with Clang-Cl, which goes actually very
nicely and already uncovered some bugs.
(Let me thank all developers that already worked on making clang-cl such a
good tool)
Unfo
