Stats

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

Ncverilog: Is there a predefined `define containing IUS version number/string?

cubicle82

In C/C++ compilers, there are predefined macros which contain a version number/string ( example: __STDC_VERSION__ )  This enables source-code to enforce minimum version-checks (in some cases.)

Is there something similar irun, so my Systemveirlog-source files can check for a minimum version of IUS?

Parents

  • Hi Shalom.

    Thanks for pointing that out. Indeed, this is a useful construct for checking design parameters are valid.

    It does not however help with the parsing / compilation phase, as the user might want to abort the parsing, or substitute different code depending on the tool version. Reasons to abort the parsing: if you're an IP provider and you know your code required IUS version 9.2.30 as a minimum, else ncvlog will generate misleading errors.

    I've seen many customers writing code like `idfef TOOL_BUG_1 ... `else ... `endif. This applies to all the major vendors by the way, not just IUS ;-)

    These things can't be handled at elaboration time... I'm really sorry we can't offer a positive answer here, rather than just saying why it won't work. We did discuss whether to ignore the LRM and add some kind of syntax to do conditional `if expressions and to abort parsin, but it's hard to justify the risk of breaking existing user code for the benefit it gives (not to mention the cost).

    Still, if enough people request such a feature (through the formal support channel) then anything can be considered...

Reply

  • Hi Shalom.

    Thanks for pointing that out. Indeed, this is a useful construct for checking design parameters are valid.

    It does not however help with the parsing / compilation phase, as the user might want to abort the parsing, or substitute different code depending on the tool version. Reasons to abort the parsing: if you're an IP provider and you know your code required IUS version 9.2.30 as a minimum, else ncvlog will generate misleading errors.

    I've seen many customers writing code like `idfef TOOL_BUG_1 ... `else ... `endif. This applies to all the major vendors by the way, not just IUS ;-)

    These things can't be handled at elaboration time... I'm really sorry we can't offer a positive answer here, rather than just saying why it won't work. We did discuss whether to ignore the LRM and add some kind of syntax to do conditional `if expressions and to abort parsin, but it's hard to justify the risk of breaking existing user code for the benefit it gives (not to mention the cost).

    Still, if enough people request such a feature (through the formal support channel) then anything can be considered...

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.