• 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. Logic Design
  3. naming on CSA module

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 63
  • Views 14486
  • 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

naming on CSA module

tompy
tompy over 14 years ago

 Hi:

     I have a datapath module, after synthesize -to_generic, there are some CSA module has been added by RC, which naming is very ugly. Both in module name and instance name.

its RTL is :assign  mout_int = smult(coeff,datain);  where smult is a function.

 and 

its instance name is : \smult_30_22:mux_59_9_g1,  I don't want "/" and ":" which is not accepted by STA tool. I can't find the option to change name. Besides re-write by design compiler, is there any option in RC I can use to replace them?

I also got ugly module name such as  \csa_tree_smult_30_22:sub_62_34_group_325

thanks for the help!

 

 

  • Cancel
Parents
  • grasshopper
    grasshopper over 14 years ago

     Hi Tompy,

     one more comment on naming attributes. Generally speaking, naming style use a default to increase "by name" compatibility with Formal tools (LEC, Formality, etc). The more you change the naming defaults without changing on the formal setup, the more likely you will see increases in runtime and potentially even aborts.

    regards,

    gh-

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

     Hi Tompy,

     one more comment on naming attributes. Generally speaking, naming style use a default to increase "by name" compatibility with Formal tools (LEC, Formality, etc). The more you change the naming defaults without changing on the formal setup, the more likely you will see increases in runtime and potentially even aborts.

    regards,

    gh-

    • 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