Subject:
|
Re: Speed of RCX interpreting bytecodes: slow
|
Newsgroups:
|
lugnet.robotics.rcx
|
Date:
|
Wed, 5 Jan 2000 03:57:07 GMT
|
Reply-To:
|
mattdm@+IHateSpam+mattdm.org
|
Viewed:
|
1384 times
|
| |
|
|
Dave Baum <dbaum@spambgoneenteract.com> wrote:
> Its been a long time since I looked at the firmware in detail, but is it
> possible that the bytecode interpreter is driven from one of the timer
> chains? If this was the case, it wouldn't matter if the CPU could execute
> the bytecode in 200 cycles...it would still just wait for the next tick
> before executing another bytecode.
Hmm. If so, an interesting option for a theoretical replacement-but-
compatible firmware to have would be the ability to do things as fast as
possible. (Of course, it'd have to be an option, since it's possible that
some badly-designed code wouldn't work properly...)
--
Matthew Miller ---> mattdm@mattdm.org
Quotes 'R' Us ---> http://quotes-r-us.org/
|
|
Message is in Reply To:
 | | Re: Speed of RCX interpreting bytecodes: slow
|
| Its been a long time since I looked at the firmware in detail, but is it possible that the bytecode interpreter is driven from one of the timer chains? If this was the case, it wouldn't matter if the CPU could execute the bytecode in 200 cycles...it (...) (25 years ago, 5-Jan-00, to lugnet.robotics.rcx)
|
11 Messages in This Thread:
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
