From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <fweimer@redhat.com>
Received: from us-smtp-delivery-124.mimecast.com
 (us-smtp-delivery-124.mimecast.com [170.10.129.124])
 by sourceware.org (Postfix) with ESMTPS id 634BD3858405
 for <gcc@gcc.gnu.org>; Tue, 23 Nov 2021 13:49:10 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 634BD3858405
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com
 [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS
 (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 us-mta-219-Oop7pKCWPg-73M8Onxmntw-1; Tue, 23 Nov 2021 08:49:06 -0500
X-MC-Unique: Oop7pKCWPg-73M8Onxmntw-1
Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com
 [10.5.11.11])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 6876B10168C4;
 Tue, 23 Nov 2021 13:49:05 +0000 (UTC)
Received: from oldenburg.str.redhat.com (unknown [10.39.192.29])
 by smtp.corp.redhat.com (Postfix) with ESMTPS id AA97A57CD3;
 Tue, 23 Nov 2021 13:49:03 +0000 (UTC)
From: Florian Weimer <fweimer@redhat.com>
To: Dmitry Vyukov via Gcc <gcc@gcc.gnu.org>
Cc: Dmitry Vyukov <dvyukov@google.com>,  ro@gcc.gnu.org,  Jakub Jelinek
 <jakub@redhat.com>,  Martin =?utf-8?Q?Li=C5=A1ka?= <marxin@gcc.gnu.org>,
 Marco Elver <elver@google.com>
Subject: Re: New ThreadSanitizer runtime (v3)
References: <CACT4Y+bvVooxDChy120qBz2jaT6=HVw+e+ZtGeaxUut4ND+FNg@mail.gmail.com>
Date: Tue, 23 Nov 2021 14:49:01 +0100
In-Reply-To: <CACT4Y+bvVooxDChy120qBz2jaT6=HVw+e+ZtGeaxUut4ND+FNg@mail.gmail.com>
 (Dmitry Vyukov via Gcc's message of "Mon, 22 Nov 2021 16:22:24 +0100")
Message-ID: <8735nnt22a.fsf@oldenburg.str.redhat.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain
X-Spam-Status: No, score=-4.5 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH,
 DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW,
 RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE,
 TXREP autolearn=unavailable autolearn_force=no version=3.4.4
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
 server2.sourceware.org
X-BeenThere: gcc@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc mailing list <gcc.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc>,
 <mailto:gcc-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <mailto:gcc-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc>,
 <mailto:gcc-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Nov 2021 13:49:11 -0000

* Dmitry Vyukov via Gcc:

> I wanted to give heads up regarding a significant re-design of the
> ThreadSanitizer runtime:
> https://reviews.llvm.org/D112603
> Currently it's submitted:
> https://github.com/llvm/llvm-project/commit/1784fe0532a69ead17793bced060a9bf9d232027
> but can well be rolled back if too many buildbots fail, but should be
> submitted again soon anyway.
>
> It was extensively tested and lots of bugs were fixed, but it's still
> possible it will cause some issues just because of the size of the
> change and OS/arch sensitivity.

Have there been changes to the glibc integration?  Does it still
hard-code the size of (private) struct pthread?

Thanks,
Florian