|
|
 | | Re: WinNT & legOS
|
| Hello again Rossz, I have downloaded lfn003 and installed it and ALL WORKED OK :o) It build the demo programs (including running makelx). So although the WinNT saga is probably not over, it mow seems to work for me (and maybe some others). Many (...) (25 years ago, 1-Feb-00, to lugnet.robotics.rcx.legos)
| | | | | Re: __attribute__ ((rcx_interrrupt)) : how to use ?
|
| (...) Well, i got the definitive answer from Markus 8-). It was in german, so i'll try to translate it: the effect of __attribute__ ((rcx_interrrupt)) depends on the calling context: - in leaf functions (that do not call other functions), it makes (...) (25 years ago, 1-Feb-00, to lugnet.robotics.rcx.legos)
| | | | | WinNT & legOS
|
| I was mistaken in thinking the Long File Name utility ((URL) was breaking makelx. The program, makelx.exe, runs perfectly if typed from the command line. When executed out of the make program, however, it thinks the command line is invalid, whether (...) (25 years ago, 1-Feb-00, to lugnet.robotics.rcx.legos)
| | | | | Re: __attribute__ ((rcx_interrrupt)) : how to use ?
|
| (...) Right. The calling conventions of the H8 say that r0-r3 are scratch registers (aka caller saves). However, interrupt handlers must preserve ALL of the registers. So the rcx_interrupt attribute makes that happen. (...) The compiler will only (...) (25 years ago, 31-Jan-00, to lugnet.robotics.rcx.legos)
| | | | | __attribute__ ((rcx_interrrupt)) : how to use ?
|
| hi there, i´m still not really sure when and why to use __attribute__ ((rcx_interrrupt)) my current assumptions: 1 - it should be used for functions that are called AS interrupt handlers, to make sure registers are pushed onto the stack, and (...) (25 years ago, 31-Jan-00, to lugnet.robotics.rcx.legos)
|
|
