Path: chuka.playstation.co.uk!news
From: "John \( QuietBloke \)" <quietbloke@btinternet.com>
Newsgroups: scee.yaroze.freetalk.english
Subject: Re: Daft Question [long]
Date: Thu, 30 Aug 2001 19:40:19 +0100
Organization: PlayStation Net Yaroze (SCEE)
Lines: 46
Message-ID: <9mm1bn$h6i8@www.netyaroze-europe.com>
References: <01c1297e$8cb6e8a0$LocalHost@pal-s-omnibook> <9lrqqf$3j63@www.netyaroze-europe.com> <01c129ca$a5a6f700$d81fe4d5@pal-s-omnibook> <9m1d9c$b2i7@www.netyaroze-europe.com> <01c12ceb$fba64880$9709e4d5@pal-s-omnibook> <9m9c88$ioj5@www.netyaroze-europe.com> <01c12edc$cc2bf440$991fe4d5@pal-s-omnibook> <9me1g1$1sb13@www.netyaroze-europe.com> <9meajl$1sb17@www.netyaroze-europe.com> <9med8s$1sb18@www.netyaroze-europe.com> <9mekaq$1sb20@www.netyaroze-europe.com> <3b915bb2.83462112@www.netyaroze-europe.com>
NNTP-Posting-Host: host213-1-131-17.btinternet.com
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200

aye.. I may never actually write anything in assembler but if your scambling
around
looking for ways to speed something up then if you have a little knowledge
you can
quite often adjust your C code to make use of it. Or am I wrong ( as
usual ).
ie.. without knowing a bit shift is fast you would probably divide by 2..
does the compiler
optimize the code to do a shift if it can ? <shrug>

John ( QuietBloke )

"Steven Osman" <sosman@terratron.com> wrote in message
news:3b915bb2.83462112@www.netyaroze-europe.com...
> Actually, it's funny you should mention your experiments...
>
> I'm sure that many of us won't be using assembly anyway, so whether or
> not the MIPS cpu is capable of more powerful instructions is
> irrelevant -- the ultimate question is "What code does the C compiler
> generate?" for a lot of us.
>
> Steven
>
> On Tue, 28 Aug 2001 00:16:16 +0100, "Jon Prestidge  (Jon@surfed.to)"
> <jon@surfed.to> wrote:
>
> >> Where'd you get that info from .. if you dont mind me asking
> >
> >I found the MIPS instruction set somewhere... I was quite surprised how
few
> >instructions there were .. I kept thinking it was just the commonly used
> >ones and there was another page of them somewhere, then I remembered what
> >'risc' was all about.
> >
> >And other than that I just experiment with writing little routines, say a
> >few lines of code, and disassemling them --- that way it's reasonably
easy
> >to see what instruction relates to what line of C code, and you can try
> >different things and see what it gets compiled into. (to start with it's
> >best to switch any compiler optimisations off)
> >
> >Jon
> >
>