From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Add some parallel_for_each tests
Date: Mon, 30 Aug 2021 07:44:24 -0600 [thread overview]
Message-ID: <87v93njbd3.fsf@tromey.com> (raw)
In-Reply-To: <90242728-b05c-81b8-c69f-f9ec60c0d77c@polymtl.ca> (Simon Marchi's message of "Mon, 30 Aug 2021 09:29:10 -0400")
Simon> I think you could mention in the commit message that the bug in question
Simon> happened when n_threads == 0, and what is was (a crash, hang, bad
Simon> result, etc).
Ok, I did that. I'm going to check it in.
Tom
next prev parent reply other threads:[~2021-08-30 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-28 19:18 Tom Tromey
2021-08-29 19:58 ` Simon Marchi
2021-08-30 2:24 ` Tom Tromey
2021-08-30 13:29 ` Simon Marchi
2021-08-30 13:44 ` Tom Tromey [this message]
2021-08-30 15:45 ` Simon Marchi
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=87v93njbd3.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).