• 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 functions with regexp

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 63
  • Views 14810
  • 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 functions with regexp

menime54
menime54 over 9 years ago

I am trying to use the get_libs command with a regular expression.  The following is returning an error for me as the regular expression is not working.  It is trying to evaluate [sft] instead of using it in the regular expression.  How do I write this line of code to work properly?

[get_libs -regexp "scs8ls_[sft][sft]_.*"]

rc:/> [get_libs -regexp "scs8ls_[sft][sft]_.*"]  
invalid command name "sft"

Thanks,


Stephanie

  • Cancel
Parents
  • grasshopper
    grasshopper over 9 years ago

    This is kinda tricky since SDC provides an application note with commands and options but nothing on semantics, etc.

    Here is how you can make it work in Innovus and Genus. I believe Innovus is 'more' correct in this case. I believe Genus is too strict in interpreting as literal when using {} to protect string

    [DEV]innovus 5> get_libs -regexp {r[ao]m.*}
    ram_256x16_slow rom_512x16A_slow ram_256x16_fast rom_512x16A_fast
    0x18

    genus@root:> get_libs -regexp "r\\\[ao\\\]m.*"
    library:wc0d99com/ram_256x16_slow library:wc0d99com/rom_512x16A_slow

    Using {} in Genus will result in nothing found since [] gets interpreted as literals. The downside of the innovus approach would be looking for libraries that have literal [] in their name would then likely require escapes, etc.

    hope this helps,

    gh-

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

    This is kinda tricky since SDC provides an application note with commands and options but nothing on semantics, etc.

    Here is how you can make it work in Innovus and Genus. I believe Innovus is 'more' correct in this case. I believe Genus is too strict in interpreting as literal when using {} to protect string

    [DEV]innovus 5> get_libs -regexp {r[ao]m.*}
    ram_256x16_slow rom_512x16A_slow ram_256x16_fast rom_512x16A_fast
    0x18

    genus@root:> get_libs -regexp "r\\\[ao\\\]m.*"
    library:wc0d99com/ram_256x16_slow library:wc0d99com/rom_512x16A_slow

    Using {} in Genus will result in nothing found since [] gets interpreted as literals. The downside of the innovus approach would be looking for libraries that have literal [] in their name would then likely require escapes, etc.

    hope this helps,

    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