Home > Community > Forums > Functional Verification > one question about e hal --ignore or delete the post plz

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

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

Last post Thu, Feb 23 2012 11:08 PM by redrabbit. 3 replies.
Started by redrabbit 22 Feb 2012 06:45 PM. Topic has 3 replies and 3097 views
Page 1 of 1 (4 items)
Sort Posts:
  • Wed, Feb 22 2012 6:45 PM

    • redrabbit
    • Top 500 Contributor
    • Joined on Tue, Nov 22 2011
    • Posts 26
    • Points 385
    one question about e hal --ignore or delete the post plz Reply

    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.

    • Post Points: 5
  • Wed, Feb 22 2012 7:17 PM

    • redrabbit
    • Top 500 Contributor
    • Joined on Tue, Nov 22 2011
    • Posts 26
    • Points 385
    Re: one question about e hal Reply

    ......,

    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?

    • Post Points: 20
  • Thu, Feb 23 2012 12:41 AM

    • StephenH
    • Top 25 Contributor
    • Joined on Tue, Sep 2 2008
    • Bristol, Avon
    • Posts 278
    • Points 4,450
    Re: one question about e hal Reply
    This is a rule that exists in many other languages. I think you'll see it in GNU C/C++ compilers for example. The risks are that you made a typo and assigned to or read from the wrong variable; that you declared a variable with the wrong name; that you forgot to implement part of your code; you're storing something for debug and consequently wasting memory... Like with most linting, the tool can't tell you what you did wrong, it doesn't understand your intent. What it can do is draw your attention to places where there might be bugs or functional / performance problems.
    Steve Hobbs / Applications Engineer / Cadence Functional Verification
    • Post Points: 20
  • Thu, Feb 23 2012 11:08 PM

    • redrabbit
    • Top 500 Contributor
    • Joined on Tue, Nov 22 2011
    • Posts 26
    • Points 385
    Re: one question about e hal Reply

    thank you StephenH!

    • Post Points: 5
Page 1 of 1 (4 items)
Sort Posts:
Started by redrabbit at 22 Feb 2012 06:45 PM. Topic has 3 replies.