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

Non-synthesizable "#1" in generated rtl #54

Closed
kdloe opened this issue Mar 5, 2019 · 6 comments
Closed

Non-synthesizable "#1" in generated rtl #54

kdloe opened this issue Mar 5, 2019 · 6 comments

Comments

@kdloe
Copy link

kdloe commented Mar 5, 2019

Is there a option to not have the "#1" in the generated rtl?

//------- reg assigns for axirdl_shm_intm
always_ff @ (posedge clk or negedge sig_ordtreg_rst_n) begin
if (! sig_ordtreg_rst_n) begin
rg_axirdl_shm_intm_err_int <= #1 1'd0;
end
else begin
rg_axirdl_shm_intm_err_int <= #1 reg_axirdl_shm_intm_err_int_next;
end
end

@sdnellen
Copy link
Contributor

sdnellen commented Mar 5, 2019

No option to remove these currently. What synth tool has issues with pound 1?

@kdloe
Copy link
Author

kdloe commented Mar 12, 2019

Not that a synth tool has an issue with it, it shows up in our LINT checks as non-synthesizable and may contribute to sim vs silicon mismatches. We have a mix of legacy verilog code and newer system verilog code and do not allow #1 due to a past history of simulators that had issues with delta delays. Even though today's tools have less issues, our methodology is that the UVCs take care of any timing issues at the verif boundary. We also do not want surprise timescale differences.

sdnellen pushed a commit that referenced this issue Mar 13, 2019
if true (default) a pound 1 delay is included in sequential assign
statements.  If false, no delay is added.  Addresses issue #54.
@sdnellen
Copy link
Contributor

Added include_sequential_assign_delays param in v190312 - set to false to remove these pound 1 delays (seems to gen correctly but not tested).

@sdnellen
Copy link
Contributor

Try release 190524.01.

@neenuprince
Copy link

Tried the new Release and we don't see the #1's anymore

@kdloe
Copy link
Author

kdloe commented Jun 7, 2019

Closing

@kdloe kdloe closed this as completed Jun 7, 2019
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

No branches or pull requests

3 participants