• 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. Functional Verification
  3. How to get the preprocessor output from irun?

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 64
  • Views 5421
  • 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

How to get the preprocessor output from irun?

Jeff000
Jeff000 over 7 years ago

I've tried 

irun -svpp 

But I was told that is is deprecated in the latest version.

Is there any way to check the preprocessor output in irun?

Thanks.

  • Cancel
  • StephenH
    StephenH over 7 years ago

    Hi.

    The irun svpp mode was deprecated several years ago. It was only ever a stop-gap to handle certain SV constructs that the Incisive parser didn't support at the time.

    If you move to Incisive version 15.20, you won't need svpp. Better still, talk to your local Cadence team about upgrading to Xcelium, which replaced Incisive at the start of 2017, it has very good SV support.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Jeff000
    Jeff000 over 7 years ago in reply to StephenH

    Thank you! So I guess Xcelium will support preprocessor output, right?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • StephenH
    StephenH over 7 years ago in reply to Jeff000

    There is no pre-processor now, all the parsing is done natively. Why do you think you need access to a preprocessor? What are you trying to do?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Jeff000
    Jeff000 over 7 years ago in reply to StephenH

    well, sometimes there're macros which are really complicated, so I think a pre-processor could help to debug in such scenario.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • muffi
    muffi over 7 years ago in reply to Jeff000

    You can use the "-parseinfo macro" option to irun/xrun.

    By default, -parseinfo macro applies globally, affecting all instances in the design. Optionally, you can limit the report by specifying a list of one or more module names.

    The macro argument provides the following information on these macro instances:

    -- The source code where the macro was used.

    -- The macro definition used to expand the macro instance.

    I hope this helps.

    • Cancel
    • Vote Up +2 Vote Down
    • Cancel
  • Jeff000
    Jeff000 over 7 years ago in reply to muffi

    Great! Thank you!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • StephenH
    StephenH over 7 years ago in reply to Jeff000

    Ah, for macros, try adding "-parseinfo macro" to see all the macros expanded in the log.

    • 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