optimize "IF B=C THEN ..." about basicv2 HOT 6 CLOSED

Yes, you are right. That was a copy and paste issue. Should be fixed now. The JAR is new as well, I hope it includes the address bytes fix now.

from basicv2.

Interesting...I'm not sure if this is applicable in all cases, though. Because Mospeed's runtime uses 0 values with a dirty mantissa in some cases. But it might not affect this...I'll take a look at it.

from basicv2.

I've added it. The implementation is slightly different from your suggestion, but it's basically the same thing. I also had to modify the runtime to make three routines that were allowing for a dirty mantissa to set the whole FAC to zero instead. I hope this covers all edge cases. Performance wise, it depends if this helps or not. A special test case with 3 IFs of which 2 could be optimized improved by around 8%.

from basicv2.

is this PR in the .jar?

from basicv2.

It should be. There might not trigger in all cases though.

from basicv2.

(ok, but I think the other PR about the addressheader is not in the JAR because I get the old command line help message).

Regarding this one, I noticed what could be an issue: the label dceloop1 is generated twice

20 A=8:A=A+1
30 IF A=8 THEN PRINT 
31 IF A<>8 THEN PRINT 

compiled:

LINE_30:
...
dceloop1:
...
BPL dceloop1
...
LINE_31:
...
dceloop1:
...
BPL dceloop1

But the label is incremented correctly if line 31 is changed into IF A=8 ...

from basicv2.