From: "Martin Liška" <mliska@suse.cz>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: gcc <gcc@gcc.gnu.org>,
ro@gcc.gnu.org, "Jakub Jelinek" <jakub@redhat.com>,
"Martin Liška" <marxin@gcc.gnu.org>,
"Marco Elver" <elver@google.com>,
"Alexander Potapenko" <glider@google.com>
Subject: Re: New ThreadSanitizer runtime (v3)
Date: Thu, 23 Dec 2021 13:10:32 +0100 [thread overview]
Message-ID: <e692ed23-713b-03ff-33aa-b03c35b54185@suse.cz> (raw)
In-Reply-To: <CACT4Y+b+cjX=RetSsT-Ut+qsyPkj8e+q7i-cC3vyy9oiPStnng@mail.gmail.com>
On 11/30/21 05:17, Dmitry Vyukov wrote:
> On Mon, 29 Nov 2021 at 19:16, Martin Liška <mliska@suse.cz> wrote:
>>
>> On 11/22/21 20:01, Dmitry Vyukov wrote:
>>> I've already reverted the change. So I will include a fix into the next version.
>>> Thanks for notifying.
>>
>> Hello.
>>
>> Am I correct that the patch set is installed again? Any near future plans for another
>> revert of the patch? Do you think it's the right time to merge it to GCC?
>
> It has been re-landed at least twice since then :)
> Well, I can't promise that it won't be reverted again. I obviously do
> not want that. Hard to say. I need to send some follow up clean up
> patches and I plan to wait till the end of the week (to avoid messy
> multi commit reverts).
> So if there are no deadlines to miss, I would suggest waiting until
> the beginning of the next week.
Hello.
May I please ask about the status of TSANv3? Note we'll flip to stage4 stage in about
3 weeks and so I'm curious if we want to do one more merge from upstream?
@Jakub: What do you think about it?
Cheers,
Martin
next prev parent reply other threads:[~2021-12-23 12:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 15:22 Dmitry Vyukov
2021-11-22 18:30 ` Martin Liška
2021-11-22 19:00 ` Dmitry Vyukov
2021-11-22 19:07 ` Martin Liška
2021-11-22 19:54 ` Marco Elver
2021-11-22 19:20 ` Jakub Jelinek
2021-11-22 18:38 ` Martin Liška
2021-11-22 19:01 ` Dmitry Vyukov
2021-11-29 18:16 ` Martin Liška
2021-11-30 4:17 ` Dmitry Vyukov
2021-12-23 12:10 ` Martin Liška [this message]
2021-12-23 12:21 ` Dmitry Vyukov
2021-11-23 13:49 ` Florian Weimer
2021-11-23 13:51 ` Dmitry Vyukov
2021-11-23 13:59 ` Florian Weimer
2021-11-23 15:37 ` Dmitry Vyukov
2021-11-23 16:16 ` Florian Weimer
2021-11-23 16:52 ` Dmitry Vyukov
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=e692ed23-713b-03ff-33aa-b03c35b54185@suse.cz \
--to=mliska@suse.cz \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=gcc@gcc.gnu.org \
--cc=glider@google.com \
--cc=jakub@redhat.com \
--cc=marxin@gcc.gnu.org \
--cc=ro@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).