Ondrej Ille

Hello @nickg do you have any news with regards to coverage? Did you happend to have a time to review it ? I am wondering whether I should start working...

Oh, thanks, I completely missed this-one. I probably should set some email notifications on my Github repos...

Hi @nickg , thanks for review, I will look at all the stuff (including your last MR), but I am swamped by my regular work duties these days, so its...

I have processed most of the remarks, still need to fix tests. I completely removed implicit labeling of branches and statements from parser, and moved it all to the coverage...

Removal of implicit statement labelling completely from parser, had only one issue in `p_component_instantiation` statement. I worked around by not inserting NULL into symbol table. Since parse error is thrown...

OK, I will do that. Btw. WBU the failing Ubuntu test? Should I implement JIT-IIR support for cover VCODE ops? Also, what is the architecture behind the JIT? I understand...

> > WBU the failing Ubuntu test? Should I implement JIT-IIR support for cover VCODE ops? > > Don't worry about that for now, I'll fix it up later. If...

On my side the MR is ready, is there something else I should look at on it? Edit: OK, I checked the MR into my fork, again, no notification, thats...

> Sorry could you change one more thing please: the constant `VCODE_VERSION` in `vcode.c` needs to be increment because some of the instructions changed in a backwards-incompatible way. Hi, no...

Hi, thanks for the reply. For the methodology of verification, I was refering to something like: Testbench with randomly generated program, and DUT state compared (e.g. post each instruction) with...