From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4455 invoked by alias); 8 Mar 2004 18:29:11 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 4434 invoked from network); 8 Mar 2004 18:29:09 -0000 Received: from unknown (HELO sccrmhc13.comcast.net) (204.127.202.64) by sources.redhat.com with SMTP; 8 Mar 2004 18:29:09 -0000 Received: from lucon.org ([24.6.43.109]) by comcast.net (sccrmhc13) with ESMTP id <20040308182907016004ii3re>; Mon, 8 Mar 2004 18:29:07 +0000 Received: by lucon.org (Postfix, from userid 1000) id 967A264A9B; Mon, 8 Mar 2004 10:29:06 -0800 (PST) Date: Mon, 08 Mar 2004 18:29:00 -0000 From: "H. J. Lu" To: binutils@sources.redhat.com, GDB Subject: What x86 TLS relocations can be in debug section? Message-ID: <20040308182906.GA29662@lucon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-SW-Source: 2004-03/txt/msg00052.txt.bz2 Intel compiler may generate some x86 TLS relocations, R_386_TLS_LE, R_386_TLS_GOTIE and R_386_TLS_IE, against debug section. The current x86 linker will try optimize R_386_TLS_GOTIE and R_386_TLS_IE. But the optimization won't work in debug section. My questions are 1. Are TLS relocations needed in debug section? 2. If not, how does gdb handle TLS? H.J.