From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 0337D3858017; Fri, 23 Sep 2022 16:44:00 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0337D3858017
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1663951441;
	bh=5LDOYBcJG0FdZuydWM/3uhkKd4ImTHhsAiFD2Mf7SW8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=In0af2U17dadFnL2CiUiHJlezSd+ukocRm/+FONybO8Fg+6HI/lnTPZyyVaAjtjKY
	 zQKcGX4lhEsSUN4CoyX+8RkbJjGx9gOxvn/e8bYdg/cMWqbanNzlNZ+ZyHWWbqda+B
	 O9fxO0mrlXpHJR3DX1R7RxdhSTDl63lbyZlV7rQ4=
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/101978] thread sanitizer false positive when
 condition variable
Date: Fri, 23 Sep 2022 16:44:00 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 11.1.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-101978-4-cfG0sABjol@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-101978-4@http.gcc.gnu.org/bugzilla/>
References: <bug-101978-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D101978

--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jakob Weisblat from comment #6)
> I think this is the same issue as
> https://github.com/google/sanitizers/issues/1259.=20
>=20
> It was fixed in clang at
> https://github.com/llvm/llvm-project/commit/
> 16eb853ffdd1a1ad7c95455b7795c5f004402e46.
>=20
> There exists an email that seems to indicate someone having submitted a G=
CC
> patch to fix this issue, but I'm not really sure what the process is for
> getting such a patch approved or included, and it seems to have been
> ignored: https://gcc.gnu.org/pipermail/gcc-patches/2021-April/568749.html
> (description) /
> https://gcc.gnu.org/pipermail/gcc-patches/2021-April/568758.html (actual
> patch)

If it is the same issue, then the fix went into GCC 12 with a (few) merge f=
rom
upstream.=