From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11730 invoked by alias); 10 Oct 2016 22:43:25 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 11718 invoked by uid 89); 10 Oct 2016 22:43:24 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=H*RU:67.222.38.55, Hx-spam-relays-external:cmgw3, Hx-spam-relays-external:10.0.90.84, H*RU:sk:gproxy5 X-HELO: gproxy5-pub.mail.unifiedlayer.com Received: from gproxy5-pub.mail.unifiedlayer.com (HELO gproxy5-pub.mail.unifiedlayer.com) (67.222.38.55) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with SMTP; Mon, 10 Oct 2016 22:43:14 +0000 Received: (qmail 3745 invoked by uid 0); 10 Oct 2016 22:43:12 -0000 Received: from unknown (HELO cmgw3) (10.0.90.84) by gproxy5.mail.unifiedlayer.com with SMTP; 10 Oct 2016 22:43:12 -0000 Received: from box522.bluehost.com ([74.220.219.122]) by cmgw3 with id tyj91t00a2f2jeq01yjCP9; Mon, 10 Oct 2016 16:43:12 -0600 X-Authority-Analysis: v=2.1 cv=KLfJUj1o c=1 sm=1 tr=0 a=GsOEXm/OWkKvwdLVJsfwcA==:117 a=GsOEXm/OWkKvwdLVJsfwcA==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=CH0kA5CcgfcA:10 a=20KFwNOVAAAA:8 a=Jx7FKj_wmZeWqZOKI_AA:9 a=_5rfeCA2p8Hzfm_y:21 a=op8kB3-v_QdOc1Tx:21 a=e_O65bzb51kRm2y5VmPK:22 Received: from 71-218-192-86.hlrn.qwest.net ([71.218.192.86]:50686 helo=bapiya) by box522.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.86_1) (envelope-from ) id 1btjHp-0008G3-Lb; Mon, 10 Oct 2016 16:43:09 -0600 From: Tom Tromey To: Jan Kratochvil Cc: Tom Tromey , gdb-patches@sourceware.org Subject: Re: [patch+7.12.1 2/2] Fix TLS (such as 'errno') regression References: <20161009185647.GB13645@host1.jankratochvil.net> <87shs4xnpd.fsf@tromey.com> <20161010151308.GA21241@host1.jankratochvil.net> Date: Mon, 10 Oct 2016 22:43:00 -0000 In-Reply-To: <20161010151308.GA21241@host1.jankratochvil.net> (Jan Kratochvil's message of "Mon, 10 Oct 2016 17:13:08 +0200") Message-ID: <87zimbomf8.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-BWhitelist: no X-Exim-ID: 1btjHp-0008G3-Lb X-Source-Sender: 71-218-192-86.hlrn.qwest.net (bapiya) [71.218.192.86]:50686 X-Source-Auth: tom+tromey.com X-Email-Count: 6 X-Source-Cap: ZWx5bnJvYmk7ZWx5bnJvYmk7Ym94NTIyLmJsdWVob3N0LmNvbQ== X-SW-Source: 2016-10/txt/msg00235.txt.bz2 >>>>> "Jan" == Jan Kratochvil writes: Jan> And I do not think it is correct to set that offset to zero for Jan> SHF_TLS as the thread initialization data is really located at the Jan> section address relocated by that PIE-load-base address. If it's useful then that makes sense. >> On the third hand it seems strange to even try to get the "address" of a >> TLS symbol in this way. Jan> There could be a symbol's getter which asserts/throws on reading Jan> address of a TLS symbol? Yes. Tom