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

back.verilog: honour write_verilog_opts. #298

Closed
wants to merge 1 commit into from

Conversation

peteut
Copy link
Contributor

@peteut peteut commented Jan 7, 2020

write_verilog_opts is not properly forwarded, this should fix that.

@codecov
Copy link

codecov bot commented Jan 7, 2020

Codecov Report

Merging #298 into master will not change coverage.
The diff coverage is 25%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #298   +/-   ##
=======================================
  Coverage   82.13%   82.13%           
=======================================
  Files          34       34           
  Lines        5647     5647           
  Branches     1160     1160           
=======================================
  Hits         4638     4638           
  Misses        864      864           
  Partials      145      145
Impacted Files Coverage Δ
nmigen/build/plat.py 26.63% <0%> (ø) ⬆️
nmigen/back/verilog.py 67.56% <50%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 476ce15...474a14e. Read the comment docs.

@whitequark
Copy link
Contributor

The current behavior is intentional. What are you trying to do?

@peteut
Copy link
Contributor Author

peteut commented Jan 7, 2020

The current behavior is intentional. What are you trying to do?

I tried to shut up Vivado by passing in some write_verilog_opts options. If the current behaviour is intentional we can close this request. Specifically I'm getting critical warnings [Netlist 29-72], there was a hint to use binary, so I passed in -nohex, but it did not help anyway:

CRITICAL WARNING: [Netlist 29-72] Incorrect value '13'b1111111111111' specified for property 'init'. Expecting type 'binary' with possible values of '1'b0,1'b1'. The system will either use the default value or the property value will be dropped. Please verify your source files. [...]

@whitequark
Copy link
Contributor

Specifically I'm getting critical warnings [Netlist 29-72], there was a hint to use binary, so I passed in -nohex, but it did not help anyway.

I agree that avoiding things like "critical warnings" from Vivado is valuable. I think this should be done by adding options to emit_verilog in the appropriate platform itself, not in your designs. If you manage to find the correct combinations of options for that, please do submit a PR adding them to vendor.xilinx_*.

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.

None yet

2 participants