public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
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: Mon, 18 Jul 2022 10:13:51 +0000	[thread overview]
Message-ID: <bug-29359-4717-Xjno3GZeYx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29359-4717@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
(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 ([=] ()
>     {
>       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.

https://sourceware.org/pipermail/gdb-patches/2022-July/190830.html

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

  parent reply	other threads:[~2022-07-18 10:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 15:20 [Bug build/29359] New: " vries at gcc dot gnu.org
2022-07-13  5:57 ` [Bug build/29359] " vries at gcc dot gnu.org
2022-07-13  6:06 ` vries at gcc dot gnu.org
2022-07-13 17:00 ` tromey at sourceware dot org
2022-07-18 10:13 ` vries at gcc dot gnu.org [this message]
2022-11-10  7:14 ` vries at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-29359-4717-Xjno3GZeYx@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).