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

Support mutable top-level parameters for --protect-lib #1522

Open
veripoolbot opened this issue Sep 24, 2019 · 2 comments
Open

Support mutable top-level parameters for --protect-lib #1522

veripoolbot opened this issue Sep 24, 2019 · 2 comments

Comments

@veripoolbot
Copy link

@veripoolbot veripoolbot commented Sep 24, 2019


Author Name: Todd Strader (@toddstrader)
Original Redmine Issue: 1522 from https://www.veripool.org

Original Assignee: Todd Strader (@toddstrader)


This may also have applications outside of --dpi-protect. Possible solutions:

  • Automatically convert parameters to wires
  • Construct parametric portions of the design at runtime

The former handles simple parameter cases, but cannot handle parameters that control generate blocks, for instance. The latter needs more thought, but since we're essentially doing the same thing for --dpi-protect itself, we may be able to continue down that path to solve this problem.

@veripoolbot

This comment has been minimized.

Copy link
Author

@veripoolbot veripoolbot commented Sep 24, 2019


Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2019-09-24T14:44:13Z


Parameters that create data types or generate if/for subcells are unlikely to ever be "wire"able, but perhaps others can. Needs detailed discussion/proposal.

@veripoolbot

This comment has been minimized.

Copy link
Author

@veripoolbot veripoolbot commented Oct 25, 2019


Original Redmine Comment
Author Name: Todd Strader (@toddstrader)
Original Date: 2019-10-25T12:11:05Z


Agreed, I'm not going to dive into anything here before we have a well baked plan.

But in the interest of writing things down, I also think that we should be able to promote the --protect-lib'ed module's paramters to the SV wrapper. That way we could do different things such as use the correct library based on the parameter configuration or pass the parameters that we've write-ified via DPI to the module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.