• 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. Custom IC SKILL
  3. How to supress Parser warnings in CIW?

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 143
  • Views 15802
  • 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 supress Parser warnings in CIW?

gs748
gs748 over 10 years ago

Hello,

Whenever I load a SKILL file in CIW Warning messages appear in CIW which does not effect the process. I do not want the Warnings to appear in CIW. Can anyone please tell me how to supress the Parser warnings from CIW whenever SKILL file is loaded.

I appreciate your help! Thanks

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 10 years ago

    Please give an example of the kind of parser warnings that you'd like to suppress. Not sure what you mean.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • gs748
    gs748 over 10 years ago

     In skill file I am running a command => system("nbstatus jobs --jobid,exitstatus,class --format csv --history 1h \"user==\'\$USER\'\")

    Below is an example of the parser warning  which I see in CIW and I want to supress  :

    PARSER WARNING at line 17 column 177 of file check.il
    *WARNING* (Parser): character found after backslash is not meaningful - nbstatus jobs-- jobid,exitstatus,class --format csv --history 1h \"user==\'\$USER\'\")

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • skillUser
    skillUser over 10 years ago

    You will need one more backslash in front of the $ - the backslash needs escaping itself, so that \$ can be output to the shell, i.e. 

    
    system("nbstatus jobs --jobid,exitstatus,class --format csv --history 1h \"user==\'\\$USER\'\")
    

    Hopefully this will help you.

    Regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 10 years ago

    Lawrence is right - fix the error in the code rather than suppressing warnings. Suppressing warnings is a very poor solution in this case.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • gs748
    gs748 over 10 years ago

    This is the command line I am using in the SKILL file:

    command => system("nbstatus jobs --jobid,exitstatus,class --format csv --history 1h \"user==\'\$USER\'\" > /tmp/out")

    Parser warning message appears 3 times as below:

    PARSER WARNING at line 17 column 177 of file check.il
    *WARNING* (Parser): character found after backslash is not meaningful - nbstatus jobs-- jobid,exitstatus,class --format csv --history 1h \"user==\'\$USER\'\" > /tmp/out")

    PARSER WARNING at line 17 column 177 of file check.il
    *WARNING* (Parser): character found after backslash is not meaningful - nbstatus jobs-- jobid,exitstatus,class --format csv --history 1h \"user==\'\$USER\'\" > /tmp/out")

    PARSER WARNING at line 17 column 177 of file check.il
    *WARNING* (Parser): character found after backslash is not meaningful - nbstatus jobs-- jobid,exitstatus,class --format csv --history 1h \"user==\'\$USER\'\" > /tmp/out")

    When I use more backslashes before the character then no warnings appear but does not do the actual process(will not dump out the output of the command in the o/p file).

    I want the command line to work without giving any warnings. Are there any other methods to do the task.



    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 10 years ago

    Yes, get your escapes correct in the first place. There's no need to escape the ' or the $:

    system("nbstatus jobs --jobid,exitstatus,class --format csv --history 1h \"user=='$USER'\" > /tmp/out")

    This should do the same as the command  you gave with the unnecessary escape characters. Your command caused a SKILL parser warning - SKILL thought you were escaping characters that don't need escaping, and so ignored the escape character; Lawrence was assuming that you wanted the escape character in the shell, and so for that you'd need to be passing a "\" to the shell, and so the backslash has to be escaped in that case. That turned out to be an incorrect assumption.

    Kindest Regards,

    Andrew.

    • 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