Julian Kemmerer

Also having examples to point to would be good

Making a `headers` directory sounds fine to me And then move dirs+files like you said `headers/axi/axis.h` for ex. `dvi/` dir was to match `vga/` which did end up having a...

I might prefer `include` as dir name over `headers` ex. `include/axi/axis.h`

Work around is to have a FIFO after the autopipelined area (or otherwise be always ready for output)... ```c #include "uintN_t.h" #include "axi/axis.h" #include "fifo.h" #include "compiler.h" #pragma MAIN_MHZ the_pipeline...

Whoops :facepalm:

Feels similar to 'these wires are not normal autopipelined w/ registers wires' like https://github.com/JulianKemmerer/PipelineC/issues/65 or https://github.com/JulianKemmerer/PipelineC/issues/66 might be getting at...

You can think of the inputs (clock enables, resets, feedback ready signals) being sampled during the pipelines first cycle And the outputs being driven from the last cycle The same...

Could maybe do something like ```c // A global wire that is the clock enable // for the entire axis_test pipeline uint1_t the_clock_enable; typedef struct axis_test_t{ uint32_t axis_out_data; uint1_t axis_out_valid;...

Sounds good - been trying to remember throw exceptions when writing recent code - sounds good. I have zero ideas for named exceptions - probably need to look at what...

To be clear it is possible today to write C functions wrapping raw VHDL that instantiated LUTs and from there you could with some extra work get the compiler to...