public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Michael Matz <matz@suse.de>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: "Menezes, Evandro" <evandro.menezes@amd.com>,
		Jan Beulich <JBeulich@novell.com>,
	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: Mon, 09 Oct 2006 06:23:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.0610090822000.4864@wotan.suse.de> (raw)
In-Reply-To: <oru02emswx.fsf@free.oliva.athome.lsd.ic.unicamp.br>

Hi Alexandre,

On Sun, 8 Oct 2006, Alexandre Oliva wrote:

> Here's an updated patch the should address all of your concerns.  The 
> proposed ABI changes haven't changed at all for almost a year, and in 
> the mean time we've ported it to one more platform (ARM), so I believe 
> this is rock solid now.

Thanks for the update.  From my perspective we should include it in the 
ABI document.  I'll wait a day or two in case there are concerns.


Ciao,
Michael. 

  reply	other threads:[~2006-10-09  6: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 [this message]
2006-10-09 19:57   ` Menezes, Evandro
2006-10-10  8:23     ` Alexandre Oliva
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=Pine.LNX.4.64.0610090822000.4864@wotan.suse.de \
    --to=matz@suse.de \
    --cc=JBeulich@novell.com \
    --cc=aj@suse.de \
    --cc=aoliva@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=discuss@x86-64.org \
    --cc=evandro.menezes@amd.com \
    --cc=libc-alpha@sources.redhat.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).