Hi all-
We are using code generation tools v6.1.13, for a C64+ core (DM648), and are shocked to find that, though the compiled (and optimized for speed) assembly shows liberal use of SPLOOP, it takes the extra step of DINT before each SPLOOP. My understanding is that, in the C64+, SPLOOP *is* interruptable, so confused why DINT/RINT coming from compiler around the loops. Actually, more than confused, totally annoyed, as we have some large image loops that take a few millisecs to process, and we miss data from the UART!
Is 6.1.13 way out of date? (we are using CCS 3.3). We tried -mixxxxx, but it caused way too many problems. What I want is for the codegen tools to utilize what the processor is capable of--SPLOOPs that are interruptable!
Please Advise,
Jim Gort