|
From: <ca...@li...> - 2019-01-05 10:59:11
|
Thanks guys for the replies. Yes I was looking for a way to activate the parse tracing features as explained here : https://www.slac.stanford.edu/comp/unix/gnu-info/bison_11.html . I have looked at the parse.output file that is generated but it shows the whole autamata which is very confusing (im extremely inexperienced with bison) whereas I would rather like to see the exact path the parser has taken at runtime, what tokens were encountered and what tokens where expected. >From my understanding the parse trace functionality if enabled correctly should show me the exact states that were followed before my syntax error occurs. For our project I hope to add multi-state UDP tables into a branch or fork of iverilog to allow more concice gate-level RSFQ logic descriptions. I could share the git diff if anyone is interested. Kind regards Calvin _______________________________________________ Iverilog-devel mailing list Ive...@li... https://lists.sourceforge.net/lists/listinfo/iverilog-devel |