Stats

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

Preserving structure in RTL Compiler

Aram Shahinyan

 Dear all,

I have a AND-OR structure written in RTL in a module. After the synthesis I see that the same logic is implemented using different logic elements in different modules. In one module I see AND-OR is formed with 4 instances, in other module with 5 instances.

Is there a way to tell RC to use exactly the same AND-OR structure in different modules, that are using same piece of RTL code?

Thanks,

Aram

Parents

  •  Sounds like all you want is to pre-compile them and script the handling in P&R. Without hierarchy for the structure in question, you will be challenged in a number of way. Nothing prevent you from pre-compiling and then reading as netlist and using set_dont_touch/preserve. It sounds like the design is extremely uniform (100K structure and hand-solution is ALWAYS best) or physical aware solution should do a reasonable job addressing your congestion concerns. I suggest you work with your local AE on this since they may be able to provide more specific advise once they see your exact situation

     happy holidays,

    gh-

     

    gh-

Reply

  •  Sounds like all you want is to pre-compile them and script the handling in P&R. Without hierarchy for the structure in question, you will be challenged in a number of way. Nothing prevent you from pre-compiling and then reading as netlist and using set_dont_touch/preserve. It sounds like the design is extremely uniform (100K structure and hand-solution is ALWAYS best) or physical aware solution should do a reasonable job addressing your congestion concerns. I suggest you work with your local AE on this since they may be able to provide more specific advise once they see your exact situation

     happy holidays,

    gh-

     

    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.