What steps will reproduce the problem?
1. Create an optimized kernel
2. RunSelf(7, smlRunStepSize.sml_PHASE) vs. ExecuteCommandLine("run --self -p
7")
3. GetDecisionCycleCounter, GetCurrentPhase
What is the expected output? What do you see instead?
Expected: identical output
Actual...
RunSelf=2, sml_INPUT_PHASE
CLI=1, sml_DECISION_PHASE
For reference, non-optimized...
RunSelf=1, sml_DECISION_PHASE
CLI=1, sml_DECISION_PHASE
Optimized run control uses sml_DirectRun (sml_KernelSML.cpp) instead of CLI and
something is different in the execution.
The above output was generated using Java SML on r12742.
Original issue reported on code.google.com by nate.der...@gmail.com on 18 Jun 2011 at 5:44
Original issue reported on code.google.com by
nate.der...@gmail.com
on 18 Jun 2011 at 5:44