New Verilog samples / update to heuristics to distinguish from Coq #7493
+103
−1
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.
Description
This pull request fixes misclassification of certain
.vVerilog files that were previously identified as Rocq Prover or Coq due to syntax edge cases. These cases include:modulekeyword is followed directly by the port list with no space (e.g.,module foo(...))`pragma protectdirectives (common in encrypted IP cores)always@orinitial@without space before the sensitivity listThe updated
heuristics.ymlpattern broadens the existing Verilog match to allow for:#and(in module declarations`pragmaas a valid Verilog preprocessor directive@inalwaysandinitialblocksTwo new
.vsamples are added to demonstrate these cases, and an existing sample (button_debounce.v) is updated to include a real-world use ofalways@.Checklist:
module_stub.v: Vivado-generated module stubencrypted_module.v: encrypted IP filebutton_debounce.v: Changealways @ (toalways@(to provide an example of the possibility of no whitespace between these operators.Supporting Evidence
always @andalways@are widely used:always @: ~618,000 resultsalways@: ~60,900 resultsalways@:1bitSDR/NCO.v#L36