Menu

#5 Double zeroes in execution trace

0.5
closed
RC1 (2)
2014-07-16
2014-07-16
No

{
myLW: {96, 96, 0, 0, 96},
victory: 1,
myOW: {96, 96, 96, 0, 96},
cycles: 79931,
size: 37,
id: 96
}
{
victory: 1,
cycles: 80000,
size: 37,
id: 99
}

Two problems:
- double zero in the execution trace of the first warrior (unless there were multiple processes - check)
- the battle obviously run the the execution limit (80000), but the engine identified it as a "draw", meaning that both had processes active, but the first one only ran for 79931 cycles. Either the cycle counting is flawed, or process die detection if flawed.

Discussion

  • Miha Vitorovic

    Miha Vitorovic - 2014-07-16
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -15,4 +15,4 @@
    
     Two problems:
     - double zero in the execution trace of the first warrior (unless there were multiple processes - check)
    -- the battle obviously run the the execution limit (80000), but the engine identified it as a "draw", meaning that both had processes active, but the firs one only ran for 79931 cycles. Either the cycle counting is flawed, or process die detection if flawed.
    +- the battle obviously run the the execution limit (80000), but the engine identified it as a "draw", meaning that both had processes active, but the first one only ran for 79931 cycles. Either the cycle counting is flawed, or process die detection if flawed.
    
     
  • Miha Vitorovic

    Miha Vitorovic - 2014-07-16
    • labels: --> RC1
     
  • Miha Vitorovic

    Miha Vitorovic - 2014-07-16

    The discrepancy in the number of cycles probably comes by not counting the execution of the DAT directive(s).

     
  • Miha Vitorovic

    Miha Vitorovic - 2014-07-16

    Execution counting should be fixed by d203bfe49c1a948805852657f7e08dd3a6606dcd.

    0 in both traces (but not on the last place) is may be caused by SPL (into uninitialized memory). Will research later.

     
  • Miha Vitorovic

    Miha Vitorovic - 2014-07-16
    • status: open --> closed
     

Log in to post a comment.