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 57A923858434; Wed, 13 Jul 2022 06:06:36 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 57A923858434
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: Wed, 13 Jul 2022 06:06:36 +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: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-29359-4717-IB7ZjcbXkb@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
X-BeenThere: gdb-prs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb-prs mailing list <gdb-prs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-prs/>
List-Help: <mailto:gdb-prs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2022 06:06:36 -0000

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

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
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.

But if we start to use thread_local memory, this could be something useful =
to
try.

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