From: "Steven J. Hill" <sjhill@realitydiluted.com>
To: Guido Guenther <agx@sigxcpu.org>
Cc: linux-mips@linux-mips.org, debian-toolchain@lists.debian.org
Subject: Re: TLS register
Date: Mon, 31 May 2004 22:17:41 -0500 [thread overview]
Message-ID: <40BBF555.6000600@realitydiluted.com> (raw)
In-Reply-To: <20040531230524.GB2785@bogon.ms20.nix>
Guido Guenther wrote:
>
> He suggested $24 (t8) another discussed possibility would be $27 (k1)
> which is already abused by the PS/2 folks for ll/sc emulation.
> Another possibility would be to reserve such a register only in the
> n32/n64 ABIs and let o32 stay without __thread and TLS forever.
> Any feedback welcome.
>
I vote for $24 (t8). LL/SC emulation is an issue and I believe some of
the exception vectors, if not all of them indirectly depend on k1. It
would take a lot of work (and testing) to rewrite the exceptions to not
utilize k1 and it would probably be a nasty performance hit in many
cases. I agree with "Screw o32" and let's move forward.
-Steve
next prev parent reply other threads:[~2004-06-01 3:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-31 23:05 TLS register Guido Guenther
2004-06-01 3:17 ` Steven J. Hill [this message]
2004-06-01 12:15 ` Ralf Baechle
2004-06-01 12:44 ` Kevin D. Kissell
2004-06-01 12:44 ` Kevin D. Kissell
2004-06-01 14:28 ` Maciej W. Rozycki
2004-06-01 19:21 ` David Daney
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=40BBF555.6000600@realitydiluted.com \
--to=sjhill@realitydiluted.com \
--cc=agx@sigxcpu.org \
--cc=debian-toolchain@lists.debian.org \
--cc=linux-mips@linux-mips.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