Stats

  • Locked Locked
  • Replies 2
  • Subscribers 61
  • Views 15042
  • 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

remove_assigns

archive

v07.10-p004_1 says to me that remove_assigns command will be obsolete in the future, because Encounter will be able to process assign statements in the netlist. However we use 3rd party backend tools which need a netlist without any assign statement.

I have following code in RTL:

assign y = x;

but the netlist still has it that:

assign y = x;

I have tried several combinations for remove_assigns but not successes. This command does not clean assigns completely.

Also, the removed assign statements are replaced with following instance names:

  bfx2 rm_assigns_buf_out_0_0(.A (in_1[0]), .Z (out_0[0]));

Is there any attribute in Cadence how to control the instance names like this?
Thanks...


Originally posted in cdnusers.org by sporadic crash
Parents

  • Hi,
    Often RC can't remove assign because of "preserve" attribute
    Try somthing like this:

    # Reset existing preserve attributes (set preserve attribute to false)
    set save_ui_respects_preserve [get_attribute ui_respects_preserve /]
    set_attribute ui_respects_preserve false /
    remove_assigns
    # Restore setting
    set_attribute ui_respects_preserve $save_ui_respects_preserve /


    Originally posted in cdnusers.org by Stalker
Reply

  • Hi,
    Often RC can't remove assign because of "preserve" attribute
    Try somthing like this:

    # Reset existing preserve attributes (set preserve attribute to false)
    set save_ui_respects_preserve [get_attribute ui_respects_preserve /]
    set_attribute ui_respects_preserve false /
    remove_assigns
    # Restore setting
    set_attribute ui_respects_preserve $save_ui_respects_preserve /


    Originally posted in cdnusers.org by Stalker
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.