From: Daniel Jacobowitz <drow@false.org>
To: "H. J. Lu" <hjl@lucon.org>
Cc: binutils@sources.redhat.com, GDB <gdb@sources.redhat.com>
Subject: Re: What x86 TLS relocations can be in debug section?
Date: Mon, 08 Mar 2004 18:31:00 -0000 [thread overview]
Message-ID: <20040308183153.GA24645@nevyn.them.org> (raw)
In-Reply-To: <20040308182906.GA29662@lucon.org>
On Mon, Mar 08, 2004 at 10:29:06AM -0800, H. J. Lu wrote:
> 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?
You could just compile a procedure using TLS and look, you know.
The debug info will tell you exactly what GCC does.
Take a look at DW_OP_GNU_push_tls_address, which is used for this
exact purpose.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-03-08 18:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 18:29 H. J. Lu
2004-03-08 18:31 ` Daniel Jacobowitz [this message]
2004-03-08 20:32 ` Richard Henderson
2004-03-09 16:39 ` H. J. Lu
2004-03-09 18:57 ` Richard Henderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040308183153.GA24645@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=hjl@lucon.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox