• 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. "Automatic" keyword supported in NCverilog6.1?

Stats

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

"Automatic" keyword supported in NCverilog6.1?

archive
archive over 18 years ago

Hello All, Do the system verilog keyword "automatic" is supported in ncverilog ver 6.1? I tried the following code program automatic test(FIFO_INF.TEST FIFO_INF_U1) // code endprogram The above gave me error, then i tried removing automatic, then the program worked fine. So want to know automatic" keyword is suported or not. Thanks & Regards, Quest Team


Originally posted in cdnusers.org by sundar_80
  • Cancel
Parents
  • archive
    archive over 18 years ago

    Hi Sundar, Automatic program is valid as per IEEE 1800 standard and I'm sure tools will support them in near future. I also recommend using automatic programs in my [b]SystemVerilog for Verification course [/b] that I deliver in Bangalore (See: www.noveldv.com). It makes life easier with several threads being spawned off with an advanced SV testbench. However as Steve said one can work it around as an interim solution. Here is LRM quote for your reference.

    program_nonansi_header ::= { attribute_instance } program [ lifetime ] program_identifier [ parameter_port_list ] list_of_ports ;
    HTH Ajeetha, CVC www.noveldv.com


    Originally posted in cdnusers.org by ajeetha
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 18 years ago

    Hi Sundar, Automatic program is valid as per IEEE 1800 standard and I'm sure tools will support them in near future. I also recommend using automatic programs in my [b]SystemVerilog for Verification course [/b] that I deliver in Bangalore (See: www.noveldv.com). It makes life easier with several threads being spawned off with an advanced SV testbench. However as Steve said one can work it around as an interim solution. Here is LRM quote for your reference.

    program_nonansi_header ::= { attribute_instance } program [ lifetime ] program_identifier [ parameter_port_list ] list_of_ports ;
    HTH Ajeetha, CVC www.noveldv.com


    Originally posted in cdnusers.org by ajeetha
    • 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