Rob Springer
Rob Springer
Right now, a proc could take a channel in its `config` function and store it as a member...it could also - at the same time - pass that channel to...
Currently, the send and receive calls in JitChannelQueue operate on raw buffers + len, e.g. `void JitChannelQueue::Send(const uint8_t* data, int64_t num_bytes);`. It might make users' lives easier if they could...
Raw DSLX functions can be AOT-compiled and run from testbenches, but Procs cannot, requiring that they be JIT-compiled on every execution (the proc runtime libs require a Proc* object). It'd...
Initially reported by hongted internally: Running the interpreter on the following proc ``` import std proc test_impl { in0: chan in ab; out0 : chan out u32; config(in0: chan in...
We had a bug recently where the bytecode interpreter failed due to a conditional branch w/a `let` statement inside (which it didn't handle correctly). This is a supported construct, so...
We can just ignore the op, of course, but collecting coverpoint info into some sort of report structure would be neat.
I'm currently adding Proc support to the frontend, but I'm punting on what it means to fail!() inside one. We will, of course, need to handle this through our stack...
This would be useful for getting _some_ idea of how long we should expect some proofs to take - it's at least a necessary first step.
Right now, an array of channels is declared as: `chan[COLS][ROWS] F32;` and one side of a channel is declared (as a proc member) as: `zeroes_out: chan out[COLS] F32;` It may...
Right now, if a TestProc has no termination condition (i.e., no send on the terminator channel), then simulation will spin infinitely. It seems possible to check to make sure that...