From: Tom de Vries <Tom_deVries@mentor.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: "gcc-patches@gnu.org" <gcc-patches@gnu.org>,
Jakub Jelinek <jakub@redhat.com>,
Dodji Seketeli <dodji@seketeli.org>,
Kostya Serebryany <kcc@google.com>,
"thread-sanitizer@googlegroups.com"
<thread-sanitizer@googlegroups.com>
Subject: Re: [RFC, PR68580] Handle pthread_create error in tsan testsuite
Date: Mon, 15 Feb 2016 08:07:00 -0000 [thread overview]
Message-ID: <56C18726.50702@mentor.com> (raw)
In-Reply-To: <CACT4Y+YfK0Cq2fZnCdSt2hO64+UWN7Hd39Cts7Vpupa8p4Sk8w@mail.gmail.com>
On 15/02/16 08:24, Dmitry Vyukov wrote:
> If we are talking about pr 68580, then I would try:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68580#c2
> first.
As I tried to explain in the follow-up comment (
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68580#c3 ), since
unfortunately I have no reliable way of reproducing the failure, there's
no defined way to 'try' something.
Thanks,
- Tom
next prev parent reply other threads:[~2016-02-15 8:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 6:01 Tom de Vries
2016-02-15 7:18 ` Dmitry Vyukov
2016-02-15 7:25 ` Dmitry Vyukov
2016-02-15 8:07 ` Tom de Vries [this message]
2016-02-15 9:07 Bernd Edlinger
2016-02-15 9:15 ` Dmitry Vyukov
2016-02-15 10:45 ` Tom de Vries
2016-02-15 10:56 ` Dmitry Vyukov
2016-02-15 11:29 ` Bernd Edlinger
2016-02-15 12:05 ` Dmitry Vyukov
2016-02-15 12:44 ` AW: " Bernd Edlinger
2016-02-15 12:46 ` Dmitry Vyukov
2016-02-15 19:26 ` Mike Stump
2016-02-15 19:34 ` Dmitry Vyukov
2016-02-18 11:36 ` Tom de Vries
2016-02-18 20:19 ` Bernd Edlinger
2016-02-18 21:31 ` Jakub Jelinek
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=56C18726.50702@mentor.com \
--to=tom_devries@mentor.com \
--cc=dodji@seketeli.org \
--cc=dvyukov@google.com \
--cc=gcc-patches@gnu.org \
--cc=jakub@redhat.com \
--cc=kcc@google.com \
--cc=thread-sanitizer@googlegroups.com \
/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).