From: Alexandre Oliva <aoliva@redhat.com>
To: "Menezes, Evandro" <evandro.menezes@amd.com>
Cc: "Jan Beulich" <JBeulich@novell.com>,
"Michael Matz" <matz@suse.de>,
discuss@x86-64.org, "Andreas Jaeger" <aj@suse.de>,
binutils@sources.redhat.com,
libc-alpha@sources.redhat.com,
"Michael Meissner" <michael.meissner@amd.com>,
"H. J. Lu" <hjl@lucon.org>
Subject: Re: RFC: TLS improvements for IA32 and AMD64/EM64T
Date: Tue, 10 Oct 2006 08:23:00 -0000 [thread overview]
Message-ID: <or4pucbmw5.fsf@free.oliva.athome.lsd.ic.unicamp.br> (raw)
In-Reply-To: <1449F58C868D8D4E9C72945771150BDF5215EF@SAUSEXMB1.amd.com> (Evandro Menezes's message of "Mon, 9 Oct 2006 14:56:35 -0500")
On Oct 9, 2006, "Menezes, Evandro" <evandro.menezes@amd.com> wrote:
> Would you consider adding the calculations for the new relocations
> in order to improve their clarity?
I can try, although relaxations make it much trickier than it might
seem.
> I remember some examples in your paper at the GCC Summit and adding
> them to section 3.5 would be swell too.
So we're talking *really* self-contained, eh? Fair enough, I'll take
a shot.
> From your paper at the GCC Summit it's quite clear that such
> additions to the psABI would be a fine idea. Perhaps HJ would like
> to consider the corresponding additions for the i386 psABI
> extension.
H.J., do you have the i386 psABI in source form somewhere I could get
it, to make the corresponding changes?
> So, there's no question about the technical part of your proposal.
> But, as you can infer from my comments above, I'd like to improve
> the clarity of the psABI so that one wouldn't have to go to specific
> implementations to figure out the details. What do you think?
Sounds like a reasonable goal.
> -+referenced symbol binds locally, the \texttt{DTPOFF} may be omitted.
> ++referenced symbol binds locally, the relocations \texttt{R_X86_64_64} and \texttt{R_X86_64_32} may be used instead.
No, in such cases the linker omits the relocation entirely, and fills
the corresponding stop with the value it can compute itself.
> +Otherwise, such relocations are always in pairs, such that the
> -+\texttt{DTPOFF64} relocation applies to the word64 right past the
> -+corresponding \texttt{DTPMOD} relocation.
> ++\texttt{R_X86_64_DTPOFF64} relocation applies to the word64 right past the
> ++corresponding \texttt{R_X86_64_DTPMOD64} relocation.
Ok, I've added R_X86_64_ everywhere I'd omitted it.
Please expect an updated patch soon.
If you'd rather install a patch with these minor modifications and
keep the more detailed patch separate, let me know and I'll send you
what I have right away.
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
Secretary for FSF Latin America http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}
next prev parent reply other threads:[~2006-10-10 8:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 23:18 Menezes, Evandro
2006-10-08 20:53 ` Alexandre Oliva
2006-10-09 6:23 ` Michael Matz
2006-10-09 19:57 ` Menezes, Evandro
2006-10-10 8:23 ` Alexandre Oliva [this message]
2006-10-10 16:24 ` Menezes, Evandro
2006-10-25 23:58 ` A public discussion group for IA32 psABI H. J. Lu
-- strict thread matches above, loose matches on Subject: below --
2005-09-17 14:14 RFC: TLS improvements for IA32 and AMD64/EM64T Menezes, Evandro
2005-09-17 18:45 ` Alexandre Oliva
2005-09-16 6:07 Alexandre Oliva
2005-09-16 7:27 ` Alexandre Oliva
2005-09-16 7:34 ` Andreas Jaeger
2005-09-16 8:19 ` Jan Beulich
2005-09-16 21:01 ` Alexandre Oliva
2005-09-18 17:17 ` Alexandre Oliva
2005-09-22 7:53 ` Alexandre Oliva
2006-01-14 17:58 ` Alexandre Oliva
2006-01-18 1:45 ` Alan Modra
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=or4pucbmw5.fsf@free.oliva.athome.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=JBeulich@novell.com \
--cc=aj@suse.de \
--cc=binutils@sources.redhat.com \
--cc=discuss@x86-64.org \
--cc=evandro.menezes@amd.com \
--cc=hjl@lucon.org \
--cc=libc-alpha@sources.redhat.com \
--cc=matz@suse.de \
--cc=michael.meissner@amd.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).