You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I need to modify gate level netlists by changing the input and output of individual gates. Currently, I'm doing this using PCRE. This is an inelegant and haphazard solution. I'd like to instead manipulate the AST generated by your parser, and then reserialize it. Is this currently supported? It does not seem to be.
If not, what do you think the best way to go about serializing the AST would be? My plan is to create tuple structs for each AST node struct which contains references to the the AST and to the node, and then implement the Display trait for these tuple structs.
I apologize if this was the wrong place to ask this question, but I did not see reference to mailing list, discord, etc.
The text was updated successfully, but these errors were encountered:
@nblei
I think the basic goal of sv-parser is to help analyze SystemVerilog source code in the project. As it constructs full AST, basically you can get all information recorded in the source code. For easier use-case, you can define your self-use verilog parser(for low-level description) to get gate information and manipulate it then. I believe you'll get inspired from the repo https://github.com/eda-rs/netlist
I need to modify gate level netlists by changing the input and output of individual gates. Currently, I'm doing this using PCRE. This is an inelegant and haphazard solution. I'd like to instead manipulate the AST generated by your parser, and then reserialize it. Is this currently supported? It does not seem to be.
If not, what do you think the best way to go about serializing the AST would be? My plan is to create tuple structs for each AST node struct which contains references to the the AST and to the node, and then implement the Display trait for these tuple structs.
I apologize if this was the wrong place to ask this question, but I did not see reference to mailing list, discord, etc.
The text was updated successfully, but these errors were encountered: