I guess I'm going to change procedure names to "cycles", unless anyone disagrees.
Matt. On Dec 28, 9:20 pm, mattschinkel <[email protected]> wrote: > Thanks, so would you rather have: > > stopwatch_read_inst() > > or > > stopwatch_read_cycles() > > Matt. > > On Dec 28, 8:48 am, Oliver Seitz <[email protected]> wrote: > > > > I made a instruction counter, although I am not sure if > > > this is the > > > correct name. Some instructions take more then 4 OSC cycles > > > right? > > > Maybe someone can suggest better naming. > > > I can't. These are called "instruction cycles", even though there are > > instructions that take more than one instruction cycle. It is in fact an > > exceptional case for RISC (i.e. PIC) processors, that most of the > > instructions only take one instruction cycle. > > > > "asm nop" gives a value of 1 > > > Great. > > > It's mainly branches, i.e. goto, call and return that take 2 or 3 > > instruction cycles with PIC processors. > > > Greets, > > Kiste > > -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
