From: Dmitry Vyukov <dvyukov@google.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: "Dmitry Vyukov via 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>,
"Fangrui Song" <maskray@google.com>
Subject: Re: New ThreadSanitizer runtime (v3)
Date: Tue, 23 Nov 2021 17:52:20 +0100 [thread overview]
Message-ID: <CACT4Y+aNEDqUixN__Jcjcmk4mAWWwXy6TiERerXRCK5u2WrdLg@mail.gmail.com> (raw)
In-Reply-To: <87a6husv8i.fsf@oldenburg.str.redhat.com>
On Tue, 23 Nov 2021 at 17:16, Florian Weimer <fweimer@redhat.com> wrote:
>
> * Dmitry Vyukov:
>
> > On Tue, 23 Nov 2021 at 14:59, Florian Weimer <fweimer@redhat.com> wrote:
> >>
> >> * Dmitry Vyukov:
> >>
> >> > Or what kind of integration do you mean? Tsan did not have any direct
> >> > integration and worked with unmodified glibc.
> >>
> >> I thought there is a false-positive data race report if an initial-exec
> >> or local-exec TLS variable is reused (whose memory is not managed by
> >> malloc).
> >
> > I don't remember any such open issues.
>
> This glibc patch submission mentions tsan:
>
> [PATCH] elf: Add __libc_get_static_tls_bounds [BZ #16291]
> <https://sourceware.org/pipermail/libc-alpha/2021-September/131388.html>
>
> It's currently stalled (adding an interface for something that may stop
> working in the future is problematic).
I see. Nothing has changed with respect to
__libc_get_static_tls_bounds with my patches.
prev parent reply other threads:[~2021-11-23 16:52 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
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 [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=CACT4Y+aNEDqUixN__Jcjcmk4mAWWwXy6TiERerXRCK5u2WrdLg@mail.gmail.com \
--to=dvyukov@google.com \
--cc=elver@google.com \
--cc=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=marxin@gcc.gnu.org \
--cc=maskray@google.com \
--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).