 | | Re: RCX "locking up" when trying to use dll
|
|
(...) It's actually in the library. I just found it. Here is a disassembly of a correct memcpy.o, as built by egcs-1.1.2: 00000000 <_memcpy>: 0: 0d 13 mov.w r1,r3 2: 09 23 add.w r2,r3 4: 1d 13 cmp.w r1,r3 6: 47 00 beq .0 (8) 8: 6c 1a mov.b @r1+,r2l (...) (25 years ago, 11-Jan-00, to lugnet.robotics.rcx.legos)
|
| |
| | RE: pbFORTH needs better uploading, docs
|
|
(...) I realized this later, and felt it would be even more confusing to clear it up! Mea Culpa again! (...) Great. I've been struggling with getting info for the FAQ together that makes it easy for all platforms to use pbForth. The goofy line-end (...) (25 years ago, 11-Jan-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: RcxCC and tabs
|
|
"Mark Rendle" <rendle2000@hotmail.com> wrote in message news:Fo5y6u.MuF@lugnet.com... (...) to (...) the (...) others (...) for the (...) with (...) I can do that in vi (and that is what I did last time I played with my RCX about a year ago), but (...) (25 years ago, 11-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: pbFORTH needs better uploading, docs
|
|
In response to a message by Ben Jackson, Ralph Hempel wrote: <snip> (...) Actually Ralph, I think that was me. :) Although there are a few things *I've* said about pbforth that I don't like, you've given your reasons for the choices you've made to a (...) (25 years ago, 11-Jan-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: RCX "locking up" when trying to use dll
|
|
Ben Jackson schrieb: (...) Some parts of legOS, especially the interrupt handlers, are less portable than they should be - they use some assembly, or my attribute((rcx_interrupt)) which I haven't verified with 2.95.2. (...) Sounds like a problem (...) (25 years ago, 11-Jan-00, to lugnet.robotics.rcx.legos)
|
