From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ot1-x32b.google.com (mail-ot1-x32b.google.com [IPv6:2607:f8b0:4864:20::32b]) by sourceware.org (Postfix) with ESMTPS id B6DC73858C2C for ; Tue, 23 Nov 2021 13:51:52 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B6DC73858C2C Received: by mail-ot1-x32b.google.com with SMTP id b5-20020a9d60c5000000b0055c6349ff22so33828366otk.13 for ; Tue, 23 Nov 2021 05:51:52 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9p+XWK2pmUCTq3GvwmGTJvogOTVdd3idoxcphJ9Qikk=; b=E+mA298rPbQPjpehfgGPVOl+nVq0L7kkstCdJLA7pdyste5uHlJeSioFe7l6HpxR+R pGZKQEQvbOujV+JYaSR0KLejuaOggU57dfNwcoIQ4+u5jPYjoEBjDZl81Dmkyh3Cc02L 7CgR79wqQs8ETe5wmqGL5W65g2mJCJ04mXW0fhi0FjpPdSdTZ8OMABYf08x6bL9CrRy0 +lYSoxP2suNuhntKUK5CupeeE1z/11X8qPgn+6F77mkhKKL3yAAhL06owHIJyo3hu10A BzhRbbj/pHUDr19XzDVYYUSF5ADuwXfn9LX02aUb3ESHHsvn5Y3xRR0r7SgnG6/Vi0uv C5tA== X-Gm-Message-State: AOAM530CKM1OnuEnKWdxgNrvMumJhVDaaOnANCjJOvjw2BRS4gDhTZP7 1n6ePsfxu0e1ik7o94K1eW4I9vkEAbfHE0K4FtrKCg== X-Google-Smtp-Source: ABdhPJxNnC3GlcjIt/uJ5gWXxKf3fD1PZu3bclCRA1qK9XLZAUlscOYBBiIennL/1NGm86lOHknfsdjcErsZbUUErjw= X-Received: by 2002:a9d:4f0e:: with SMTP id d14mr4548600otl.137.1637675511824; Tue, 23 Nov 2021 05:51:51 -0800 (PST) MIME-Version: 1.0 References: <8735nnt22a.fsf@oldenburg.str.redhat.com> In-Reply-To: <8735nnt22a.fsf@oldenburg.str.redhat.com> From: Dmitry Vyukov Date: Tue, 23 Nov 2021 14:51:40 +0100 Message-ID: Subject: Re: New ThreadSanitizer runtime (v3) To: Florian Weimer Cc: Dmitry Vyukov via Gcc , ro@gcc.gnu.org, Jakub Jelinek , =?UTF-8?Q?Martin_Li=C5=A1ka?= , Marco Elver Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-18.3 required=5.0 tests=BAYES_00, DKIMWL_WL_MED, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, USER_IN_DEF_DKIM_WL, USER_IN_DEF_SPF_WL autolearn=ham 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2021 13:51:54 -0000 On Tue, 23 Nov 2021 at 14:49, Florian Weimer wrote: > > * 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? Hi Florian, No changes to direct glibc integration. Or what kind of integration do you mean? Tsan did not have any direct integration and worked with unmodified glibc. > Does it still hard-code the size of (private) struct pthread? I am not aware of any such hard-code.