• 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. performance: constraints list of lists

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 65
  • Views 12625
  • 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

performance: constraints list of lists

Gabv
Gabv over 7 years ago

Hi,

I'm trying to get the best performance from constrained a list of list of mvl (data_l) to a list of list of bit (data) ; pseudocode: data[i][j] = ((data_l[i][j] == MVL_1 ) ? 1:0) 
Simulator used Xcelium.

Currently the code looks like this

struct if4_bit_list_s { l: list of bit; };
struct if4_bus_type_s {
l: list of mvl; keep for each (d) in l { soft d in [MVL_0, MVL_1]; };
};

.............

data_l: list of if4_bus_type_s;
keep for each (d) in data_l {
for each in d.l {soft it in [MVL_0, MVL_1];};
};

data: list of if4_bit_list_s;

............

keep gen (data_l) before (data); --0
keep data_l.size() == data.size(); --1
keep for each (d) using index (idx) in data_l {
data_l[idx].l.size() == data[idx].l.size();
};
keep for each (d) using index (idx) in data_l {
for each in d.l { --2
it == MVL_1 => data[idx].l[index] == 1; --3
it != MVL_1 => data[idx].l[index] == 0; --4
}; --5
};

Replacing the second "for each" block (2:5) with
data[idx].l == read_only(mvl_to_bits(d.l , {MVL_1}).copy()) ; results in constrain failure to lists size (1 is failing) .

As far I can see on debugger the data_l is not fully generated (value inside data_l are not constrain to MVL_0 or MVL_1 yet) when size constraint between data and data_l (1) come into play although data_l should be generated first (0).

Replacing the (3) and (4) with
data[idx].l[index] == (it == MVL_1).as_a(bit);


results in less cpu time consumption (self / self+) : from (3.5 / 14.01) to (3.13 / 9.38) ; 

Is there a way to write the generation of data from data_l better/optimal   (maybe get rid of second "for each" somehow )? 

  • 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