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 44A1D3857803; Tue, 25 Jul 2023 14:09:04 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 44A1D3857803
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1690294144;
	bh=/XdkhGcuVpjCJekJEs72RA2ZgFblCMticSVl6Bkyxbs=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=OxJmcG2yITmUqVVAgaSZXCoJFd8EHeqNGPhlZMikEZBDDEEGFHwUFVozZoM8MTPje
	 ljVjiWygmY1Q9jY08iuRaA3WWzriIp8Xjm9kpv1BFdk3BJ1moTnRhK//PlHc58eUU/
	 3GuxkNrahJxiTEB5IsFR0ZDsnU3x/6ydpFgQhU/M=
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/110799] [tsan] False positive due to
 -fhoist-adjacent-loads
Date: Tue, 25 Jul 2023 14:09:03 +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: 13.1.1
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: cc
Message-ID: <bug-110799-4-4DNYKeDl6x@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110799-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110799-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=3D110799

Alexander Monakov <amonakov at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |amonakov at gcc dot gnu.org

--- Comment #5 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #1)
> We consider introducing load data races OK, what's the difference here?=20
> There are other passes that would do similar things but in practice the
> loads would be considered to possibly trap so the real-world impact might=
 be
> limited?

What are the examples of other transforms that can introduce data races?

This trips Valgrind's data race detector (valgrind --tool=3Dhelgrind) too. =
So I
don't think checking SANITIZE_THREAD is the correct approach.=