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

Fix a bug in the tidy-check UnusedSensitiveSignal #1056

Open
wants to merge 13 commits into
base: master
Choose a base branch
from

Conversation

JoelSole-Semidyn
Copy link
Contributor

This PR adds a simple fix to ensure that the body kind is the correct one when accessing the body attributes

JoelSole-Semidyn and others added 13 commits June 27, 2024 16:07
This new check enforces that each always_comb block is named
This new check enforces that each generate block is named.
This also is applied to the for block
This check ensures that no module instantiation uses the sintax '.var' in
the port connection, and ensures that '.var(var)' is used instead
Now, when '.*' is used with the NoDotStarInPortConnection check enabled,
the warning will be located where the '.*' character is, instead of the
location of the module that was being called.
This new check enforces that no generate block is used in the code,
since it is an old system verilog syntax
This new synthesis check ensures that if there is a conditional
block with reset, all the assignments must be either inside the
if or else statements.
This new check verifies that every signal inside the sensitivity list
of an 'always' or 'always_ff' block is used inside the block
statement. The only exception is the clock signal
* slang-tidy fix OnlyAssignedOnReset and RegisterHasNoReset:
This commit will ensure that both checks will no longer be ignoring the
configuration setting 'resetIsActiveHigh' and the possible negation of
the reset signal. Two test cases have also been added to consider this
bug.

* The error location of the warnings generated by the
OnlyAssignedOnReset and RegisterHasNoReset are now more precise and
target the variable instance where the error is found instead of the
variable declaration.
Added a simple fix to ensure that the body kind is the correct one when
accessing the body attributes
…dev/slang-tidy

* 'master' of https://github.com/MikePopoloski/slang:
  Update CHANGELOG.md
  [slang] Fix PLA task concatenation ascending order (MikePopoloski#1047)
  [slang] Fix PATHPULSE limit values (MikePopoloski#1048)
  Handle recursive parameter definitions via hierarchical reference
  Mark fmt lib headers as system headers to suppress warnings
  Bump dependency versions: fmt and pybind11
  [slang] Make string simple type (MikePopoloski#1049)
  Update README.md (MikePopoloski#1046)
  [slang][port] Fix bugs (MikePopoloski#1043)
  Use [[likely]] / [[unlikely]] replace macro SLANG_LIKELY/SLANG_UNLIKELY (MikePopoloski#1038)
  Add multiple slang-tidy checks and minor fixes in existing ones (MikePopoloski#1040)
  chore: update pre-commit hooks (MikePopoloski#1041)
Copy link

codecov bot commented Jul 12, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.71%. Comparing base (4dee9aa) to head (3b79e10).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1056   +/-   ##
=======================================
  Coverage   94.71%   94.71%           
=======================================
  Files         191      191           
  Lines       47664    47664           
=======================================
  Hits        45144    45144           
  Misses       2520     2520           

Continue to review full report in Codecov by Sentry.

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

@likeamahoney
Copy link
Contributor

I think a test case proving the fix is ​​needed

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