Stats

  • Locked Locked
  • Replies 5
  • Subscribers 62
  • Views 4103
  • 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

No binary/Encrypted TCL(tcl compiler) support in all cadence tools, but Yes in Synopsys!

iceda

 Currently everybody is talking out IP protection, including all TCL commands, but it seems that Cadence didn't do good job for this kind of IP proctection unlike synopsys. Now all byte-code TCL is supported very well in all synopsys tools, but not a tiny support in all cadence tools!

Parents
  • grasshopper

     Hi iceda,

     while it is my understanding that the byte-code compiled code from TCLPro can be provided with the decryption utility embedded as well, it is still a proprietary solution specific to TCLPro and not consistent amongst all TCLCompilers. I am curious what is your driving motivation to use this solution as opposed to the industry standard encryption provided by IEEE1800 and available in all Cadence tools as well as many other vendors. I am sure you are well aware that byte-compilation and encryption are not necessarily the same things and while TCLPro byte-compiled code provides some encryption, it may not be as robust of an encryption solution.

     gh-

Reply
  • grasshopper

     Hi iceda,

     while it is my understanding that the byte-code compiled code from TCLPro can be provided with the decryption utility embedded as well, it is still a proprietary solution specific to TCLPro and not consistent amongst all TCLCompilers. I am curious what is your driving motivation to use this solution as opposed to the industry standard encryption provided by IEEE1800 and available in all Cadence tools as well as many other vendors. I am sure you are well aware that byte-compilation and encryption are not necessarily the same things and while TCLPro byte-compiled code provides some encryption, it may not be as robust of an encryption solution.

     gh-

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.