linux-mips
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: PATCH: Fix ll/sc for mips (take 3)

from [Dominic Sweetman] [Permanent Link][Original]
To: "H . J . Lu" <hjl@lucon.org>
Subject: Re: PATCH: Fix ll/sc for mips (take 3)
From: Dominic Sweetman <dom@algor.co.uk>
Date: Mon, 4 Feb 2002 16:46:07 +0000
Cc: Dominic Sweetman <dom@algor.co.uk>, cgd@broadcom.com, linux-mips@oss.sgi.com
In-reply-to: <20020204083115.C13384@lucon.org>
References: <Pine.GSO.3.96.1020201124328.26449A-100000@delta.ds2.pg.gda.pl> <20020201102943.A11146@lucon.org> <20020201180126.A23740@nevyn.them.org> <20020201151513.A15913@lucon.org> <20020201222657.A13339@nevyn.them.org> <1012676003.1563.6.camel@xyzzy.stargate.net> <20020202120354.A1522@lucon.org> <mailpost.1012680250.7159@news-sj1-1> <yov5ofj65elj.fsf@broadcom.com> <15454.22661.855423.532827@gladsmuir.algor.co.uk> <20020204083115.C13384@lucon.org>
Sender: owner-linux-mips@oss.sgi.com
User-agent: SEMI/1.13.7 (Awazu) CLIME/1.13.6 (中ノ庄) MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386-redhat-linux) 
H . J . Lu (hjl@lucon.org) writes:

> I can change glibc not to use branch-likely without using nop. But it
> may require one or two instructions outside of the loop. Should I do
> it given what we know now?

I would not recommend using "branch likely" in assembler coding, if
that's what you're asking.

Dominic
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: PATCH: Fix ll/sc for mips (take 3), H . J . Lu
Next by Date:  madplay on mips, Pete Popov
Previous by Thread:  Re: PATCH: Fix ll/sc for mips (take 3), H . J . Lu
Next by Thread:  Re: PATCH: Fix ll/sc for mips (take 3), H . J . Lu
Indexes:  [Date] [Thread] [Top] [All Lists]