From: Nigel Stephens <nigel@mips.com>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>, ralf@linux-mips.org
Cc: dan@debian.org, macro@linux-mips.org, linux-mips@linux-mips.org
Subject: Re: [PATCH] fast path for rdhwr emulation for TLS
Date: Fri, 08 Sep 2006 18:39:08 +0100 [thread overview]
Message-ID: <4501AABC.1050009@mips.com> (raw)
In-Reply-To: <20060711.122014.52129937.nemoto@toshiba-tops.co.jp>
moto wrote:
>
>> BTW, if the fast emulation can't handle rdhwr in a delay slot, please
>> report a bug on GCC asking it not to put rdhwr in delay slots by
>> default. It's probably worthwhile.
>>
>
> If rdhwr was on a delay slot, the slow emulation will be more slower.
> So I think rdhwr should not be put on delay slot anyway regardless
> fast emulation.
>
> I asked on GCC bugzilla a few days ago but can not got feedback yet.
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28126
>
In spite of the GCC issue, is this patch now at the point where it could
be applied, or at least queued?
Nigel
next prev parent reply other threads:[~2006-09-08 17:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 15:00 [PATCH] fast path for rdhwr emulation for TLS Atsushi Nemoto
2006-07-07 15:22 ` Maciej W. Rozycki
2006-07-07 16:12 ` Atsushi Nemoto
2006-07-07 16:43 ` Atsushi Nemoto
2006-07-07 17:04 ` Maciej W. Rozycki
2006-07-07 18:22 ` Ralf Baechle
2006-07-07 16:58 ` Maciej W. Rozycki
2006-07-08 16:12 ` Atsushi Nemoto
2006-07-10 14:40 ` Atsushi Nemoto
2006-09-14 17:28 ` Ralf Baechle
2006-09-15 3:09 ` Atsushi Nemoto
2006-07-10 14:55 ` Atsushi Nemoto
2006-07-11 2:53 ` Daniel Jacobowitz
2006-07-11 3:20 ` Atsushi Nemoto
2006-09-08 17:39 ` Nigel Stephens [this message]
2006-09-09 13:56 ` Atsushi Nemoto
2006-09-10 22:30 ` Nigel Stephens
2006-09-11 5:04 ` Atsushi Nemoto
2006-09-11 8:50 ` Atsushi Nemoto
2006-09-11 9:49 ` Thiemo Seufer
2006-09-11 14:13 ` Atsushi Nemoto
2006-09-11 15:17 ` Thiemo Seufer
2006-09-11 13:09 ` Maciej W. Rozycki
2006-09-11 14:30 ` Atsushi Nemoto
2006-09-11 17:53 ` Maciej W. Rozycki
2006-09-12 1:55 ` Atsushi Nemoto
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=4501AABC.1050009@mips.com \
--to=nigel@mips.com \
--cc=anemo@mba.ocn.ne.jp \
--cc=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=ralf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.