From: Daniel Jacobowitz <dan@debian.org>
To: Kumba <kumba@gentoo.org>
Cc: libc-ports@sources.redhat.com,
Linux MIPS List <linux-mips@linux-mips.org>
Subject: Re: [PATCH]: R10000 Needs LL/SC Workaround in Glibc
Date: Tue, 27 Jan 2009 10:29:24 -0500 [thread overview]
Message-ID: <20090127152924.GA16379@caradoc.them.org> (raw)
In-Reply-To: <4928D912.4050103@gentoo.org>
On Sat, Nov 22, 2008 at 11:16:18PM -0500, Kumba wrote:
> Here's try #2. The gcc-side is already sent in and accepted. If I'm
> still missing anything, please let me know!
>
> Joshua Kinard
> Gentoo/MIPS
> kumba@gentoo.org
>
>
> 2008-11-22 Joshua Kinard <kumba@gentoo.org>
>
> * ports/sysdeps/mips/bits/atomic.h
> (R10K_BEQZ_INSN, R10K_NOPS_INSN): Define depending on ISA.
> (__arch_compare_and_exchange_xxx_32_int): Replace 'beqz' insn with
> R10K_BEQZ_INSN and add R10K_NOPS_INSN.
> (__arch_compare_and_exchange_xxx_64_int): Likewise
> (__arch_exchange_xxx_32_int): Likewise
> (__arch_exchange_xxx_64_int): Likewise
> (__arch_exchange_and_add_32_int): Likewise
> (__arch_exchange_and_add_64_int): Likewise
Thinking about this...
MIPS I: 28 NOPs is really horrid. Not so much on this processor if
the code is all in cache, but I guess that older/simpler processors
are going to sit for a number of cycles chewing through those NOPs.
Are distributions still building MIPS I code? Can we assume that
people who want to run glibc on an R10K can at least get something
for MIPS II?
MIPS II, MIPS III, MIPS IV: Using beqzl does not seem particularly
horrid - although it's still a shame since this branch is in fact
anti-likely. It will almost never be taken.
Other platforms: !(MIPS II or MIPS III or MIPS IV) is not the same as
(MIPS I)! Please don't activate this workaround on builds that won't
run on an R10K, like MIPS32.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-01-27 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 5:01 [PATCH]: R10000 Needs LL/SC Workaround in Glibc Kumba
2008-11-01 7:33 ` Kumba
2008-11-01 11:26 ` Ralf Baechle
2008-11-04 7:16 ` Kumba
2008-11-01 17:23 ` James Perkins
2008-11-04 7:16 ` Kumba
2008-11-23 4:16 ` Kumba
2009-01-27 15:29 ` Daniel Jacobowitz [this message]
2009-01-27 16:13 ` Maciej W. Rozycki
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=20090127152924.GA16379@caradoc.them.org \
--to=dan@debian.org \
--cc=kumba@gentoo.org \
--cc=libc-ports@sources.redhat.com \
--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 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.