| To: | hjl@lucon.org (H . J . Lu) |
|---|---|
| Subject: | Re: PATCH: Fix ll/sc for mips (take 3) |
| From: | Hartvig Ekner <hartvige@mips.com> |
| Date: | Sat, 2 Feb 2002 21:49:29 +0100 (MET) |
| Cc: | justinca@ri.cmu.edu (Justin Carlson), dan@debian.org (Daniel Jacobowitz), macro@ds2.pg.gda.pl (Maciej W. Rozycki), machida@sm.sony.co.jp (Hiroyuki Machida), libc-alpha@sources.redhat.com, linux-mips@oss.sgi.com, gcc@gcc.gnu.org |
| In-reply-to: | <20020202120354.A1522@lucon.org> from "H . J . Lu" at Feb 02, 2002 12:03:54 PM |
| Sender: | owner-linux-mips@oss.sgi.com |
H . J . Lu writes: > Does everyone agree with this? If yes, I can make a patch not to use > branch likely. But on the other hand, "gcc -mips2" will generate code > using branch likely. If branch likely doesn't buy you anything, > shouldn't we change gcc not to generate branch likely instructions? I would say it's still too early to actively remove them. There are many processors out there (certainly in the embedded world most of them) without branch prediction, and for all of those branch-likelys actually help performance. /Hartvig |
| Previous by Date: | Re: PATCH: Fix ll/sc for mips (take 3), H . J . Lu |
|---|---|
| Next by Date: | Re: me vs gas mips64 relocation, Daniel Jacobowitz |
| 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), Justin Carlson |
| Indexes: | [Date] [Thread] [Top] [All Lists] |