From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id C1EDA3858D1E; Thu, 10 Nov 2022 07:14:40 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C1EDA3858D1E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1668064480;
	bh=oeOAjQAadn1zQ4mPnResVXpuLdKEeam1rJbjegverbQ=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=I4Heklplpij2bGzo0W6RKDFS91+XJvc6fHMLL+9lDmZ9jaV5a74X1npVjb7AI01Km
	 CJNJOfZZvqRUhVGbwi8kro6PmGAp0c3cuOCo5Zv7GMdwIrOPPwOKBvJG6VUGq428k8
	 cl5SIv+eDspcQOheK1nao+gP5qu2JItsZrKgpGrg=
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/29359] [gdb/build] Flush out thread sanitizer issues
Date: Thu, 10 Nov 2022 07:14:40 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: build
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: 13.1
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_status target_milestone resolution
Message-ID: <bug-29359-4717-HeTGBlP7mT@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-29359-4717@http.sourceware.org/bugzilla/>
References: <bug-29359-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gdb-prs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D29359

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
   Target Milestone|---                         |13.1
         Resolution|---                         |FIXED

--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #3)
> (In reply to Tom de Vries from comment #2)
> > Another idea I had was to make sure that this in parallel_for:
> > ...
> >   /* Process all the remaining elements in the main thread.  */
> >   return results.finish ([=3D] ()
> >     {
> >       return callback (first, last);
> >     });
> > ...
> > is not run on the main thread, but only in the thread pool, to maximize=
 the
> > skew between main thread and parallel for, but given that the parallel =
for
> > waits for the elements to finish, I don't expects any results from this
> > currently.
> >=20
> > But if we start to use thread_local memory, this could be something use=
ful
> > to try.
>=20
> https://sourceware.org/pipermail/gdb-patches/2022-July/190830.html

This was not deemed acceptable in review.

I've done all I could think of, so I'm marking this task done, even though
there are no actual resulting commits.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=