From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ot1-x32e.google.com (mail-ot1-x32e.google.com [IPv6:2607:f8b0:4864:20::32e]) by sourceware.org (Postfix) with ESMTPS id E74843858409 for ; Tue, 23 Nov 2021 16:52:37 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org E74843858409 Received: by mail-ot1-x32e.google.com with SMTP id 35-20020a9d08a6000000b00579cd5e605eso4015939otf.0 for ; Tue, 23 Nov 2021 08:52:37 -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=Fps3WrhqkoKA7AREr4RfM2dKrhi/L1KVaS7vLY5Kk68=; b=O4pE3QKApPbJEhQ4HYtzWRCO8t7SjKtLujlrg6JHHulgzuptRogqd5solSqkfY4a3Z z8LprJ6n3yzYeNK1i3iCgTL7DxBqiTfowAP1oFda9PJlm1E9ZLOKRQLkxh3hOYfIG2DJ MKzNd32LPQox6F6wfhbuBcSE2EHX8CRoa0MIe3ASSzl4feaO+7QPGCV264WAlViJJjxe 3v4Ua6iszirJu8K2p6GozX7j4rDZDEx5BEITOq2k+QY+QSbbM8yKB39+ydlBY8RGYD4y eHC5vAD4WaOq5mE1O/2tb/svlIM3bzOMMlyXcS4jXVqZ+WH83aWgH8C2edU0rtF8mJrX f4UA== X-Gm-Message-State: AOAM533nVxb2AayI3QYLnBHkhTL3qzmj7CnujOaGHKmx+xvKYYfgu0jE hUZpYrKHqljaMWPUhzS+PgICta61mg3mMZJuBaN1vg== X-Google-Smtp-Source: ABdhPJyjnKnzalmuoAmcCPXAEyDjjG/LvqxPCxRA74GUjRjzgijW0SUDUJjDx7UrXeZnWgymSRDQqNNvPyOfqCPEARk= X-Received: by 2002:a05:6830:2425:: with SMTP id k5mr5818009ots.319.1637686352273; Tue, 23 Nov 2021 08:52:32 -0800 (PST) MIME-Version: 1.0 References: <8735nnt22a.fsf@oldenburg.str.redhat.com> <87y25frn0k.fsf@oldenburg.str.redhat.com> <87a6husv8i.fsf@oldenburg.str.redhat.com> In-Reply-To: <87a6husv8i.fsf@oldenburg.str.redhat.com> From: Dmitry Vyukov Date: Tue, 23 Nov 2021 17:52:20 +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 , Fangrui Song Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-17.8 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=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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2021 16:52:39 -0000 On Tue, 23 Nov 2021 at 17:16, Florian Weimer wrote: > > * Dmitry Vyukov: > > > On Tue, 23 Nov 2021 at 14:59, Florian Weimer 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] > > > 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.