• 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. one question about e hal --ignore or delete the post pl...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 65
  • Views 1166
  • 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

one question about e hal --ignore or delete the post plz

redrabbit
redrabbit over 13 years ago

hi all,

       the verification enviroment has complete and i created the senarios which i could figure out,now i want to check my code style or something with the cadence tool---hal.

       it help me a lot ,but there is one error makes my so confused.

    EAVDNA: Variable xxx is declared, and is written in  at xxx line in yyy.e file but not read.

here is one example in ehal.pdf

:

In the following example, var g is written, but not read:
struct bar_s {
a : int;
foo() is {
var g : int ;
g = a;
};
};
In the following example, var g is both read and written:
struct bar_s {
a : int;
b : int;
foo() is {
var g : int ;
g = a;
b = g;
};
};

i want to ask why??the problem is so usual in my code ,what is the risk?

thank you in advance.

redrabbit.

  • Cancel
Parents
  • redrabbit
    redrabbit over 13 years ago

    ......,

    i found one  intention of this rule is to help the usr find the variables defined but not use it properly, delete the redundancy.....

    am i right?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • redrabbit
    redrabbit over 13 years ago

    ......,

    i found one  intention of this rule is to help the usr find the variables defined but not use it properly, delete the redundancy.....

    am i right?

    • 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