From: Tom Tromey <tom@tromey.com>
To: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom de Vries <tdevries@suse.de>
Subject: Re: [PATCH][gdbsupport] Avoid main thread in parallel for with thread sanitizer
Date: Wed, 21 Sep 2022 10:09:19 -0600 [thread overview]
Message-ID: <87y1uc3e1c.fsf@tromey.com> (raw)
In-Reply-To: <20220718100520.GA26230@delia.home> (Tom de Vries via Gdb-patches's message of "Mon, 18 Jul 2022 12:05:22 +0200")
>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
Tom> When running tasks in a parallel for, some elements may be handled by a worker
Tom> thread and others by the main thread.
Tom> When running with -fsanitize=thread, avoid the main thread in the parallel
Tom> for, to prevent multi-threading problems being hidden.
Tom> Tested on x86_64-linux, with -fsanitize=thread.
Tom> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29359
Tom> Any comments?
I tend to think that different behavior based on the use of a sanitizer
should be avoided. Otherwise, the sanitizer is not checking what is
actually run.
Tom
prev parent reply other threads:[~2022-09-21 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 10:05 Tom de Vries
2022-07-18 10:31 ` Tom de Vries
2022-09-21 16:09 ` Tom Tromey [this message]
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=87y1uc3e1c.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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).