Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Preserve port order in module instantiation #839

Merged
merged 11 commits into from
Feb 21, 2020
Merged

Preserve port order in module instantiation #839

merged 11 commits into from
Feb 21, 2020

Conversation

leonardt
Copy link
Collaborator

@leonardt leonardt commented Feb 6, 2020

Updates for leonardt/verilogAST-cpp#39 so that
the order of ports for module instances are preserved. The old logic
used a std::map which uses lexical order, causing the output to sort
the ports based on the names. Migrating to a std::vector preserve's
CoreIR's internal ordering of the ports (which is based on insertion
order)

Updates for leonardt/verilogAST-cpp#39 so that
the order of ports for module instances are preserved.  The old logic
used a std::map which uses lexical order, causing the output to sort
the ports based on the names.  Migrating to a std::vector preserve's
CoreIR's internal ordering of the ports (which is based on insertion
order)
@rsetaluri
Copy link
Collaborator

See leonardt/verilogAST-cpp#39. I think this is a good change but we should lock it into the spec, so that the generated verilog doesn't keep changing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants