Conversation
|
When I added compiler optimizations back then, the time required for the compilation increased to an unacceptable level. As you removed the timeout invocation, I am curious if you have actually run the benchmarks with -O2? |
|
Yes, I have run the benchmarks Yes, it is quite challenging for scmlcc to handle this many parallel children. I just thought a long compilation time was better than no result. But some of the tests takes quite some time for uscxml also. For example the fast LCCA.256 takes 30s to initialize and the fast Transitions.256 takes 56s. (on my machine) - see log below I have now put the timeout back on and increased it to 2 minutes. This allows more of the tests to complete for both uscxml and scxmlcc. What do you think of that?
|
|
The fast implementation precalculates all predicates, whereas the large interpreter calculates and caches them on the fly. I’ll merge and update the graphs as soon as I have some time on my hands. I’ll leave this open as a reminder to myself. |
scxmlcc is designed to make the compiler able optimize away empty actions, etc.
For this to work, optimizations must be enabled, so the scxmlcc test program really should be compiled with -O2 when testing performance.