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

New rules for compatibility with Verilog 2001 #270

Merged
merged 13 commits into from
Nov 20, 2023
Merged

Conversation

DaveMcEwan
Copy link
Contributor

This collection of simple new rules is to catch the easy mistakes when you need to write code compatible with IEEE1364-2001. Of course, it won't catch everything but it finds the most common things (in my experience).

  • 2 renames:
    • non_ansi_module -> module_nonansi_forbidden
    • level_sensitive_always -> general_always_no_edge
  • New rules:
    • module_ansi_forbidden
    • general_always_level_sensitive - Similar to general_always_no_edge but allows always @*.
    • operator_self_assignment - forbids +=, -=, etc.
    • operator_incdec - forbids ++ and --.
    • keyword_forbidden_logic
    • keyword_forbidden_always_comb, keyword_forbidden_always_ff, keyword_forbidden_always_latch
    • blocking_assignment_in_always_at_edge - Similar to blocking_assignment_in_always_comb but for always @(posedge clk).
    • non_blocking_assignment_in_always_no_edge - Similar to non_blocking_assignment_in_always_comb.
  • And a new ruleset designintentV2001 to bring it all together.

@dalance
Copy link
Owner

dalance commented Nov 20, 2023

Thanks!
All rules looks good.

@dalance dalance merged commit 73ceb61 into dalance:master Nov 20, 2023
@DaveMcEwan DaveMcEwan deleted the V2k1 branch December 10, 2023 18:17
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.

2 participants