Test this out and hopefully you will recreate the fringe burst cmd issue glitch:
Change line ~117 in spatial/core/src/spatial/lang/DRAMTransfersInternal.scala so that the else condition of the if (spatialConfig.enablePIR) check gives the same as spatialConfig.enablePIR either way.
If you run Tensor4D with args 32 2 2 2 with retime turned on and the above change done, it should fail because the third from last and last bursts that the accel receives are wrong. If you turn off retiming or undo the change above, the app passes.
Test this out and hopefully you will recreate the fringe burst cmd issue glitch:
Change line ~117 in spatial/core/src/spatial/lang/DRAMTransfersInternal.scala so that the
else
condition of theif (spatialConfig.enablePIR)
check gives the same as spatialConfig.enablePIR either way.If you run Tensor4D with args 32 2 2 2 with retime turned on and the above change done, it should fail because the third from last and last bursts that the accel receives are wrong. If you turn off retiming or undo the change above, the app passes.