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,
On 1/30/20 12:02 PM, Mario Charest via cfe-users wrote:
Hello,
First post, be gentle ;-)
I'm trying to find a clean solution to an error message that
clang-tidy is giving, tried with 10 and 11)
This is the code:
struct Foo
{
Foo(const std::string &value) : m_name(value) {}
Foo(
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,
On Wed, 2020-02-05 at 19:30 +0100, JVApen wrote:
> 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 t
Le mer. 5 févr. 2020 09 h 48, Chris Green a écrit :
> Hi,
> On 1/30/20 12:02 PM, Mario Charest via cfe-users wrote:
>
> Hello,
>
> First post, be gentle ;-)
>
> I'm trying to find a clean solution to an error message that clang-tidy is
> giving, tried with 10 and 11)
>
> This is the code:
>
> str
