New rules for compatibility with Verilog 2001 #270
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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).
non_ansi_module
->module_nonansi_forbidden
level_sensitive_always
->general_always_no_edge
module_ansi_forbidden
general_always_level_sensitive
- Similar togeneral_always_no_edge
but allowsalways @*
.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 toblocking_assignment_in_always_comb
but foralways @(posedge clk)
.non_blocking_assignment_in_always_no_edge
- Similar tonon_blocking_assignment_in_always_comb
.designintentV2001
to bring it all together.