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

Create a built in construct and move module/cell parameters out of the metadata #145

Open
thunder-hammer opened this issue Jun 17, 2021 · 1 comment

Comments

@thunder-hammer
Copy link
Collaborator

It would be nice to add the parameters into the intermediate representation direction. Currently to do a cross language conversion from EDIF to Verilog or vice versa requires the composer to look at all possible locations for parameters.

It would be nice if we added a definition.parameters and a instance.parameters call. These could in turn keep track of all possible locations for parameters ie "EDIF.parameters" or "VERILOG.Parameters" (check capitalization here)

This could clean up the metadata and make parsing and composing simpler. We should at the very least allow the usage of EDIF.parameters as a key to the metadata for backward compatibility and we should probably maintain verilog.parameters as well.

In version 2.0 it would be nice to move this out of the metadata entirely.

@thunder-hammer thunder-hammer added this to Ideas in Ideas for future releases via automation Jun 17, 2021
@thunder-hammer
Copy link
Collaborator Author

My first comment wouldn't be the only way to do this, it could be a new place in the meatadata for parameters. It would just be nice to untie them from a particular language.

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

No branches or pull requests

1 participant