Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 4153
  • 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

suppressing "function <functionNameHere> redefined" output text

mtwadeCU

I have a procedure that defines a few procedures inside of it (even though I just learned there is no such thing as local functions in SKILL). Everything works fine until I call this procedure from a pcDefinePCell script. I get a message that the pcell generated information, and I can view the information in a temporary file. When I view the file, it just contains the list of functions that were redefined. Is there a way to suppress this output? It causes issues e.g. when you go to compile pcells (flashing yellow x because it interprets it as a pcell eval fail) and stream them out to gds (streamout fails because it thinkgs the pcell eval failed). 

Thanks,
Mark

Parents

  • Andrew,

    Thanks for the response!

    My problem seems to be that I'm not using any functions using SKILL++ language mode. So, what I was intending to be local procedures are written as SKILL language mode (.il) and have global scope. Thus, they get redefined every time. 

    I implemented things such that the procedure with local procedures is in SKILL++ and just called from SKILL language mode. This seems to fix things and get the behavior I want. Thanks for the suggestion!

    Mark

Reply

  • Andrew,

    Thanks for the response!

    My problem seems to be that I'm not using any functions using SKILL++ language mode. So, what I was intending to be local procedures are written as SKILL language mode (.il) and have global scope. Thus, they get redefined every time. 

    I implemented things such that the procedure with local procedures is in SKILL++ and just called from SKILL language mode. This seems to fix things and get the behavior I want. Thanks for the suggestion!

    Mark

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.