• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. problem with e linting with hal

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 65
  • Views 15339
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

problem with e linting with hal

myonlyscreen
myonlyscreen over 12 years ago

 Hi all

I am using HAL for e linting and facing a problem with filtering source file for linting.

I am using the a design_info.txt file method to filter files that i don't want to lint.

however, this method works only for the built-in rules and doesn't affect the user defined rules (rules created by me).

Is there a way to fix this behavior of the HAL linter ?   i saw that there is a way to use a callback method for HAL messages, is this the only way to deal with this problem ?

Thanks in advance.

E.M. 

  • Cancel
Parents
  • myonlyscreen
    myonlyscreen over 12 years ago

     Hi Hannes

    my irun command is very similar to yours, but i used yours to check if it will works and it doesn't.

    It still doesn't recognize the rule i want to filter.

    I am using a local def file that includes the hal.def file with include default line.

    I tried to filter the rule with the next code in the design_info file:

    lint_checking file = /some_path/e/*/e/*.e {
       EAEVWS     off;
       ETCMWS     off;
    }

    the first rule is  a built in rule thus being filtered the second one gives the following warning:

    hal: *W,NORUCY (/some_path/design_info_e_lint.txt,8|0): The argument 'ETCMWS' in lint pragma does not map to any rule or category.

    however in the Analysis summary it appears with no problems(underlined):

     Errors   : (273)
      EAEVNU (3)      EAEVWS (16)     EAGLOV (7)      EALDIB (3)
      EALIAF (5)      EALPIB (2)      EANEDR (3)      EAOUTP (49)
      EAVDUN (1)      ERARSG (17)     ERCHEX (5)      ERPKIM (1)
      ETCMWS (154)    UVBTNU (1)      UVTFRN (6)

    what do you think is the cause for difference between us ? can it be the fact that i am using a local def file ?

    it seems like the loacl def file is being loaded after the design info file.

    thanks a lot for help so far.

    E.M. 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • myonlyscreen
    myonlyscreen over 12 years ago

     Hi Hannes

    my irun command is very similar to yours, but i used yours to check if it will works and it doesn't.

    It still doesn't recognize the rule i want to filter.

    I am using a local def file that includes the hal.def file with include default line.

    I tried to filter the rule with the next code in the design_info file:

    lint_checking file = /some_path/e/*/e/*.e {
       EAEVWS     off;
       ETCMWS     off;
    }

    the first rule is  a built in rule thus being filtered the second one gives the following warning:

    hal: *W,NORUCY (/some_path/design_info_e_lint.txt,8|0): The argument 'ETCMWS' in lint pragma does not map to any rule or category.

    however in the Analysis summary it appears with no problems(underlined):

     Errors   : (273)
      EAEVNU (3)      EAEVWS (16)     EAGLOV (7)      EALDIB (3)
      EALIAF (5)      EALPIB (2)      EANEDR (3)      EAOUTP (49)
      EAVDUN (1)      ERARSG (17)     ERCHEX (5)      ERPKIM (1)
      ETCMWS (154)    UVBTNU (1)      UVTFRN (6)

    what do you think is the cause for difference between us ? can it be the fact that i am using a local def file ?

    it seems like the loacl def file is being loaded after the design info file.

    thanks a lot for help so far.

    E.M. 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information