 | | WinLNP Issues
|
|
I'm trying to compile WinLNP, and I've run across a baffling problem: h:\program files\microsoft visual studio\vc98\include\...til.h(101) : fatal error C1001: INTERNAL COMPILER ERROR (compiler file 'msc1.cpp', line 1786) Please choose the Technical (...) (23 years ago, 20-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: code
|
|
(...) [snip] (...) Can't see anything glaringly obvious, except you've used different priorities for your tasks. As they're infinite loops with no waiting, it's probably better to make their priorities equal. But the best way is probably to do all (...) (23 years ago, 19-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | RE: H8/300 Assembler/C interface
|
|
(...) Ahhh, that makes it awkward with the RCX ROM calls, but I'm pretty sure I can make my assembler source compatible with this. I'm just getting ready to release an assembler RCX serial library that is either polled or interrupt driven. Any (...) (23 years ago, 19-Apr-01, to lugnet.robotics.rcx)
|
| |
| | Re: H8/300 Assembler/C interface
|
|
(...) By the caller? No. They are callee-save. -Kekoa (23 years ago, 19-Apr-01, to lugnet.robotics.rcx)
|
| |
| | RE: H8/300 Assembler/C interface
|
|
(...) Thanks Kekoa. One more question, are the other registers r3,r4,r5,r6 considered volatile across a function call in GCC? Cheers, Ralph (23 years ago, 19-Apr-01, to lugnet.robotics.rcx)
|
| |
| | code
|
|
Hi,I'm trying to run 2 infinate loops at the same time. Is this possible? this is an example of what I'm trying to do. thanks #include <unistd.h> #include <dmotor.h> #include <dsensor.h> #include <conio.h> #include <time.h> pid_t fun_a; pid_t fun_c; (...) (23 years ago, 19-Apr-01, to lugnet.robotics.rcx.legos)
|
| |
| | Re: H8/300 Assembler/C interface
|
|
(...) Yeah, you are right. My bad. -Kekoa (23 years ago, 19-Apr-01, to lugnet.robotics.rcx)
|
| |
| | RE: H8/300 Assembler/C interface
|
|
(...) Not necessarily, that's why I'm asking. If the caller cleans up the stack, then the function just does an RTS and the caller adjusts the stack because it knows how much stuff was pushed on. For programs with lots of calls, this generates extra (...) (23 years ago, 19-Apr-01, to lugnet.robotics.rcx)
|
| |
| | Re: H8/300 Assembler/C interface
|
|
(...) Also: - caller cleans up parameters on stack - stack pointer is r7 The caller must clean up stack parameters b/c the return address is pushed after parameters are. -Kekoa (23 years ago, 18-Apr-01, to lugnet.robotics.rcx)
|
| |
| | Re: H8/300 Assembler/C interface
|
|
(...) Somebody correct me if I'm wrong. I just compiled some programs to check this. I believe that maybe the *ROM* calling convection is as Ralph described, but almost definitely the GCC calling convention is: - r0, r1, r2 hold parameters from left (...) (23 years ago, 18-Apr-01, to lugnet.robotics.rcx)
|
