-
Notifications
You must be signed in to change notification settings - Fork 8
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
yosys-slang ignoring verilog_defaults #74
Comments
Hi Dan, let me make this a feature request. The defines are accessible to a plugin, the defaults are not. I will discuss with the Yosys team if they prefer exposing the defaults for me, or going with separate defines/defaults commands for yosys-slang. |
Having looked into it a bit more, I'm inclined towards the following: With To the degree that the same option exists on all
|
Just to note: at the moment there's no integration of the slang frontend with |
I've implemented slang_defaults in d686d51, once the tests pass I will push to master. With |
Err, verilog_defines not verilog_defaults in the above comment (I've edited it) |
Hello! Not sure if this is a bug or feature request, but I'm trying to make a generic yosys-slang flow by passing in a set of variables to a synthesis script. However, it appears that yosys-slang expects me to pass in -I during the read_slang command itself. I can work around this by constructing the TCL command and executing it, but I think it would be simpler to use the verilog_defines / verilog_defaults that already exist. I know Surelog used to define another set of variables: systemverilog_defines and systemverilog_defaults, so there may be some issue with overloading that I'm unaware of. Or is there another methodology I should be using here? Thanks!
yosys.tcl
The text was updated successfully, but these errors were encountered: