• 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. Custom IC Design
  3. *Error* eval: code size too big inside a construct (32767...

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 125
  • Views 13881
  • 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

*Error* eval: code size too big inside a construct (32767 max; 32771 given)!

Jameel
Jameel over 14 years ago

Hi,

I have a simple skill script as below

load("co_ord_list.il")

foreach( crd_inst crd_list

       dbCreateInstByMasterName(cvid  src_lib  src_cell  "layout"  nil crd_inst "R0" 1)

 );end foreach
 

 

the co_ord_list.il is a simple file that creates a variable called crd_list  whis is a list of co-ordinates like code below.

crd_list = list(
  list( -60770.0 73220.0 )
  list( -56650.0 73220.0 )
  list( -54590.0 73220.0 )
  list( -52530.0 73220.0 )
  list( -50470.0 73220.0 )
  list( -48410.0 73220.0 )
  list( -46350.0 73220.0 )

.

.

.

.

 

)

 

The problem is I have a huge number of co-ordinates ~200,000 pairs and I get  *Error* eval: code size too big inside a construct (32767 max; 32771 given)!

 

 

I can work around the problem by splitting the  co_ord_list.il into smaller chunks but it was wondering if there is any simpler solution.

 

Thanks,

-Jameel

 

  • Cancel
Parents
  • skillUser
    skillUser over 14 years ago

    Hi Jameel,

    You are probably hitting one of two limitations; there is a maximum size (code vector) for SKILL in terms of lines per procedure, let, or presumably in this case lines within your list assignment, or another limitation is the number of points that a single polygon can have. So it is probably necessary to split the points into smaller lists for these two reasons. Not much help I know, but I believe this is the answer.

    Regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • skillUser
    skillUser over 14 years ago

    Hi Jameel,

    You are probably hitting one of two limitations; there is a maximum size (code vector) for SKILL in terms of lines per procedure, let, or presumably in this case lines within your list assignment, or another limitation is the number of points that a single polygon can have. So it is probably necessary to split the points into smaller lists for these two reasons. Not much help I know, but I believe this is the answer.

    Regards,

    Lawrence.

    • 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