• 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. forall and endpoint/ended

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 64
  • Views 974
  • 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

forall and endpoint/ended

archive
archive over 18 years ago

The module below has 2 assumption examples (one using endpoint and one using ended()).  In each of them, I am trying to only allow responses to addresses that have already had requests made to them.

Before forall support, a stable, undriven signal was used for the index in properties like the ones below.  Now, with forall support, I'm trying to come up with a more portable and complete solution.  However, both properties fail in the compilation.  Can someone explain the "undeclared identifier"s problem?  There only seems to be a "undeclared" problem inside of ended or endpoint.

Thanks!

module test
#(
parameter
MEM_D=8,
ADDR_W=3
)
(
input clk,
input rq_valid,rs_valid,
input [ADDR_W-1:0] rq_addr,rs_addr

);

//psl endpoint rq_to_rs(const i)=
// {rq_valid & rq_addr==i;~(rs_valid & rs_addr==i)[*] ; rs_valid & rs_addr==i}
//;

//psl assume_good_rs0: assume
// forall i in {0:MEM_D-1}: always(
// {rs_valid & rs_addr==i} |->
// {rq_to_rs(i)}
//)@(posedge clk);

//psl assume_good_rs1: assume
// forall i in {0:MEM_D-1}: always(
// {rs_valid & rs_addr==i} |->
// {ended({rq_valid & rq_addr==i;~(rs_valid & rs_addr==i)[*] ; rs_valid & rs_addr==i})}
//)@(posedge clk);


endmodule

Error with module above:
$ ifv test.v -s
ifv: 05.83-s001: (c) Copyright 1995-2007 Cadence Design Systems, Inc.
file: test.v
// {ended({rq_valid & rq_addr==i;~(rs_valid & rs_addr==i)[*]rs_valid & rs_addr==i})}
                               |
ncvlog: *E,UNDIDN (test.v,27|31): 'i': undeclared identifier ?.5(IEEE)].
// {ended({rq_valid & rq_addr==i;~(rs_valid & rs_addr==i)[*]rs_valid & rs_addr==i})}
                                                       |
ncvlog: *E,UNDIDN (test.v,27|55): 'i': undeclared identifier ?.5(IEEE)].
// {ended({rq_valid & rq_addr==i;~(rs_valid & rs_addr==i)[*]rs_valid & rs_addr==i})}
                                                                                 |
ncvlog: *E,UNDIDN (test.v,27|81): 'i': undeclared identifier ?.5(IEEE)].
        module worklib.test:v
                errors: 3, warnings: 2
ncvlog: *F,NOTOPL: no top-level unit found, must have recursive instances.
ncverilog: *E,VLGERR: An error occurred during parsing.  Review the log file for errors with the code *E and fix those identified problems to proceed.  Exiting with code (status 2).
ifv: *F,EXEERR: Errors encountered, exiting FormalVerifier. Check formalverifier.log for details.

Error if assume_good_rs1 is commented out.
$ ifv test.v -s
ifv: 05.83-s001: (c) Copyright 1995-2007 Cadence Design Systems, Inc.
file: test.v
// {rq_to_rs(i)}
|
ncvlog: *E,UNDIDN (test.v,21|0): 'assume_good_rs0_forgen_0__i': undeclared identifier ?.5(IEEE)].
        module worklib.test:v
                errors: 1, warnings: 1
ncvlog: *F,NOTOPL: no top-level unit found, must have recursive instances.
ncverilog: *E,VLGERR: An error occurred during parsing.  Review the log file for errors with the code *E and fix those identified problems to proceed.  Exiting with code (status 2).
ifv: *F,EXEERR: Errors encountered, exiting FormalVerifier. Check formalverifier.log for details.


Originally posted in cdnusers.org by weberrm
  • Cancel
  • archive
    archive over 18 years ago

    Just for an update for this issue. The problem seems to be a bug in the forall implementation when the forall index is used in any of the PSL built-in functions, ended() or prev() or whatever. The index is not recognized as having been declared. For what it is worth, the problem isn't in IFV itself, but appears in their language parser. It has been reported to Cadence R&D.


    Originally posted in cdnusers.org by TAM
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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