On 08/05/18 22:57, Jd Lyons via OpenBIOS wrote:
Yes, I have the Fcode detok(ed), but really I’m muddling around in stuff I don’t understand very well.
I have some understanding of C and a pretty good understanding of the nVidia Fdcode Option Roms, but when it comes down to raw forth I still don’t even really understand the basics.
I suspect that it's something within that branch failing which is only visible at the final b(>resolve) once the condition is evaluated, so with indentation:
4010035 fff81e54 : b?branch [ 0x14 ] (offset) 26 4010039 fff57240 : (compile) [ 0x9bd ] 401003a fff57244 : (compile) b(lit) [ 0x10 ] 401003f fff5724c : (compile) and [ 0x23 ] 4010041 fff57250 : (compile) my-space [ 0x103 ] 4010042 fff57254 : (compile) + [ 0x1e ] 4010044 fff57258 : (compile) [ 0xa08 ] 4010045 fff5725c : (compile) b(lit) [ 0x10 ] 401004a fff57264 : (compile) and [ 0x23 ] 401004b fff57268 : (compile) b(lit) [ 0x10 ] 4010050 fff57270 : (compile) = [ 0x3c ] 4010051 fff57274 : (compile) b?branch [ 0x14 ] (offset) 9 4010054 fff5727c : (compile) b(') [ 0x11 ] 4010057 fff57284 : (compile) b(to) [ 0xc3 ] 401005a fff57290 : (compile) b(>resolve) [ 0xb2 ] 401005b fff57290 : (compile) b(>resolve) [ 0xb2 ]
Most of that looks fairly normal, so I'd start by looking at the 0x9bd and 0xa08 FCodes which will have been generated further up in your output file.
I suspect you'll end up converting chunks of FCode back into Forth to figure out which part is failing.
ATB,
Mark.