From: "François Dumont" <frs.dumont@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Bug libstdc++/62313] Data race in debug iterators
Date: Tue, 30 Sep 2014 18:02:00 -0000 [thread overview]
Message-ID: <542AF019.2090407@gmail.com> (raw)
In-Reply-To: <20140930153241.GK4197@redhat.com>
I forgot to check pretty printer tests indeed, I will.
François
On 30/09/2014 17:32, Jonathan Wakely wrote:
> On 26/09/14 11:05 +0100, Jonathan Wakely wrote:
>> On 26/09/14 00:00 +0200, François Dumont wrote:
>>>
>>>>> Apart from those minor adjustments I think this looks good, but I'd
>>>>> like to know that it has been tested with -fsanitize=thread, even if
>>>>> only lightly tested.
>>>>>
>>>>>
>>>
>>> Hi
>>>
>>> Dmitry, who reported the bug, confirmed the fix. Can I go ahead
>>> and commit ?
>>
>> Yes, OK.
>
> This caused some failures in the printer tests:
>
> Running
> /home/jwakely/src/gcc/gcc/libstdc++-v3/testsuite/libstdc++-prettyprinters/prettyprinters.exp
> ...
> FAIL: libstdc++-prettyprinters/debug.cc print deqiter
> FAIL: libstdc++-prettyprinters/debug.cc print lstiter
> FAIL: libstdc++-prettyprinters/debug.cc print lstciter
> FAIL: libstdc++-prettyprinters/debug.cc print mpiter
> FAIL: libstdc++-prettyprinters/debug.cc print spciter
>
>
next prev parent reply other threads:[~2014-09-30 18:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-62313-19885@http.gcc.gnu.org/bugzilla/>
[not found] ` <bug-62313-19885-GBoNocJyMm@http.gcc.gnu.org/bugzilla/>
2014-09-10 20:55 ` François Dumont
2014-09-21 22:04 ` Jonathan Wakely
2014-09-23 20:42 ` François Dumont
2014-09-23 20:46 ` Marek Polacek
2014-09-25 22:01 ` François Dumont
2014-09-26 10:05 ` Jonathan Wakely
2014-09-30 15:32 ` Jonathan Wakely
2014-09-30 18:02 ` François Dumont [this message]
2014-09-30 20:18 ` François Dumont
2014-10-01 12:13 ` Jonathan Wakely
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=542AF019.2090407@gmail.com \
--to=frs.dumont@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.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).