Ted
From some quick internet sleuthing, it looks like these warning can be produced when the ClassWriter instance doesn't have ClassWriter.COMPUTE_FRAMES set. I see a bunch of references to ClassWriter and...
Thanks, Ben. I tried to git-diff those two tags in the r8 repo and there was way too much to look at; I'll try to come up with some bisect...
Thanks, Ben. I'm marking this P2 for now; I'll try to jump back on this after a few more things clear off my plate.
XLS git hash is 14d5f6e7ba1fd553cdfc9a0d5cb772c1c3ea75cf
Quick thought dump: really what needs to happen is that XLS-generated RTL should have the ability to flow-control the input and output interfaces. A simple ready/valid handshake with data should...
I see #578 as a subset of this issue. AXI4 and other handshake-based memory-mapped IO protocols can actually be built with just a few FIFO handshake primitives (i.e. AXI4 can...
I very briefly took a stab at this and found a couple obstacles: * csmith generates a lot of different types of code that I suspect are not supported by...
@cdleary XLScc was failing fast enough - iteration time was not the issue, but rather just getting the frontend to pass. I hadn't even gotten to the ac_int part yet....
Alternatively, if there's an XLScc flag that tells the frontend to not choke on string.h, stdint.h etc that would be great too!
@JoshVarga @spurserh Poked around with this a little more, couple updates: * Recent updates to xlscc have added some basic system library support. There's basically enough to get a csmith-generated...