• 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. RTL Compiler command questions: pwd, multicore options,...

Stats

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

RTL Compiler command questions: pwd, multicore options, and program name

menime54
menime54 over 9 years ago

Hi,

We are switching over to RTL Compiler.  I am moving our scripts over to the RTL Compiler flow.

1)  When I type pwd into RTL Compiler I get back /  .  I need the path where I started RTL Compiler, similar to doing a pwd in linux.  Is there a command to get the full path and not just the path from where you started RTL Compiler?

2)  The following option is not available in RTL Compiler.  How do I set the multicore CPU option in RTL Compiler?

set_host_options -max_cores 2

3)  Is there an RTL Compiler command that is similar to the synopsys command:  synopsys_program_name

Thanks,


Stephanie

  • Cancel
  • grasshopper
    grasshopper over 9 years ago

    Hi Stephanie,

    (1)

    To determine the path in the unix hierarchy where RC/Genus is executing, the command is 

    lpwd  (stands for local pwd)

    pwd would point to the RC (or Genus legacy mode) internal hierarchy

    (2) 

    attribute is 'max_cpus_per_server'

    In addition, user can also configure attribute 'super_thread_servers' when using multiple hosts

    (3)

    I am assuming this does the same as

    legacy_genus:/> get_attr program_name /
    Genus(TM) Synthesis Solution
    legacy_genus:/> get_attr program_short_name /
    genus
    legacy_genus:/> get_attr program_version /
    15.10
    legacy_genus:/> info nameofexecutable
    /home/tools/15.10/bin/linux/genus

    hope this helps,

    gh-

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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