Stats

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

 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!

 

 

  • Any reason you cannot use change_names to address whatever limitatios the downstream tools may have ?

    regards,

    gh-

  •  Hi gh:

                      Thanks for the help. I did not find this command before you mentioned it.I search for lots of attributes and don't know there is a command for it.

                        But I am still curious if there is command/attribute such as "hdl_use_if_generate_prefix" which can constraint the tool "before" the elaboration.

    thanks!

     

    /tompy

  •  Hi Tompy,

     > apropo names

    > apropo naming

     should show you all attributes and commands witth such words in their names or their help strings. As per a specific attribute to control naming exclusively for functions, there is no such thing documented that I am aware of. If your STA does not support the current syntax for functions, or anything else for that mattter, why not use change_names and ensure that your output, whether from functions or anything else, is STA friendly? Seems like a more comprehensive solution to me

     regards,

    gh-

  •  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-

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.