Julian Kemmerer

Need to take into account how many times writes and reads occur to the RAM and what order they occur in read first write first etc And properly wire data...

Hows this syntax? ```c typedef struct a_dual_port_ram_t { uint32_t read(uint32_t addr); void write(uint32_t addr, uint32_t data_in); uint32_t the_ram[128]; } a_dual_port_ram_t; void my_func(uint32_t raddr, uint32_t waddr, uint32_t wdata) { static a_dual_port_ram_t...

Oh also a starter version using https://stackoverflow.com/questions/29572623/plot-networkx-graph-from-adjacency-matrix-in-csv-file https://github.com/JulianKemmerer/PipelineC/blob/5685a873caebfc3b46454640617108684783cbe7/src/C_TO_LOGIC.py#L1294 exists but looks worse than yosys example above so didnt use

Maybe something like blocky gannt chart looking could work too..

I added a little info to the 'how the compiler works' about the flow through the tool, steps, architecture of everything https://github.com/JulianKemmerer/PipelineC/wiki/How-does-the-compiler-work%3F#tool-architecture-overview Could start making 'units' out of that functionality...

Also @Datavenia feel free to add info on style and tests to the new contrib file as they get into use (opening another PR still easy for this stuff?) idk...

And to be clear I currently test by by hand Running recent example code and checking that it works Running some Verilator based tests for math / floating point stuff...

rachitnigam was saying > Maybe it would be useful to have some continuous testing to keep the examples up to date! For example, we use [runt](https://github.com/rachitnigam/runt) to do this very...

Maybe we could setup tests that just run pipelinec on a bunch of the example .c files and see if it dies or not - produces a certain output idk

I would say leave code as is if it seems done for performance. It should be one of the last things to change. Focus your changes on easy code that...