-
Notifications
You must be signed in to change notification settings - Fork 234
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
Add support for vvp extended arguments #653
Comments
All simulation backends support plusargs, but they are specified in the parameters section instead so that they can be used for any simulator. Here is an example of how to define a plusarg and how to enable it in a target As for other extended arguments, such as -vcd or -lxt, those are support through the |
In the source code, |
Hmm... in all my years of using Icarus I had completely missed that. As I understand it though, you could still pass these options as plusargs. The only difference between passing Worst case we can add extended options if we need to. Just want to make sure that we can't solve it with the existing options first. |
https://man.archlinux.org/man/vvp.1.en#EXTENDED_ARGUMENTS
VVP supports "extended arguments", which can be used to pass runtime information such as plusargs to the simulation. Looks like it is not currently possible to pass these in using fusesoc (https://fusesoc.readthedocs.io/en/stable/ref/capi2.html#icarus).
The extended arguments come after the
inputfile
in the command line, but thevvp_options
from the fusesoc core file seem to come before the input file.Is this something that fusesoc should support? I'm open to contribute this feature if it is desired.
The text was updated successfully, but these errors were encountered: