public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
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
Subject: Re: RFC: TLS improvements for IA32 and AMD64/EM64T
Date: Sat, 17 Sep 2005 18:45:00 -0000	[thread overview]
Message-ID: <oroe6ryeqx.fsf@livre.oliva.athome.lsd.ic.unicamp.br> (raw)
In-Reply-To: <84EA05E2CA77634C82730353CBE3A8430346A945@SAUSEXMB1.amd.com>

On Sep 16, 2005, "Menezes, Evandro" <evandro.menezes@amd.com> wrote:

> Alexandre, 
>> Here's a patch for the x86-64 ABI document that adds the new 
>> relocations and references the new dynamic table numbers, 
>> referring to the latest version of my specs on the web for details.

> Please add the respective calculations and coding examples.

Please read the document referenced in the patch, for starters.  In it
you'll see the exact spelling of the coding samples is not final yet,
and it doesn't make sense to maintain yet another copy of this until
it settles down.  Also, you'll find that the calculations are not
quite possible to express in the way other relocations are expressed;
suggestions are welcome.  Finally, what's wrong with following the
existing practice of referring to TLS specs elsewhere?

The point of this posting was more to reserve the relocation numbers
for these purposes (the purpose of the relocations is quite solid
already, even though the numbers have changed as recently as
yesterday), but I'm yet to do some more performance tests with some
minor variations of the code sequences to choose the best one.  I
don't want to have to maintain all this information in sync between
multiple specs documents and the several different packages that
implement them; having a single specs document is much better for now.

Thanks for your, ehrm, valuable feedback :-/

-- 
Alexandre Oliva         http://www.lsd.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}

  reply	other threads:[~2005-09-17 14:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-17 14:14 Menezes, Evandro
2005-09-17 18:45 ` Alexandre Oliva [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2006-10-10 16:24       ` Menezes, Evandro
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=oroe6ryeqx.fsf@livre.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=libc-alpha@sources.redhat.com \
    --cc=matz@suse.de \
    /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).