• 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. fork and automatic

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 66
  • Views 14874
  • 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

fork and automatic

sevent
sevent over 14 years ago

 The followign code does not compile with ncverilog (the file has a .sv extension):

... 
  foreach(i[idx])
  begin
    fork
    automatic string jdx = idx;
    begin
      run(jdx);
    end
    begin
      $display("jdx = %s",jdx);
    end
    join_none
  end
... 

ncverilog gives:

 ncvlog: *E,UNSAUT (autoloop.sv,50|23): The 'automatic' keyword is not supported in this context.

 

  • Cancel
Parents
  • TAM1
    TAM1 over 14 years ago

    I haven’t seen the source code where you’ve used the automatic keyword. So it very well may be legal in the context in which it appears. There are several places where it is legal, but our simulator isn’t ready to process it yet. If you are trying to declare a variable local to a task or function automatic, try declaring the function as a whole automatic. I gave an example in the forum thread referenced in the link below.

    Tom Murray

    thomasm@cadence.com

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • TAM1
    TAM1 over 14 years ago

    I haven’t seen the source code where you’ve used the automatic keyword. So it very well may be legal in the context in which it appears. There are several places where it is legal, but our simulator isn’t ready to process it yet. If you are trying to declare a variable local to a task or function automatic, try declaring the function as a whole automatic. I gave an example in the forum thread referenced in the link below.

    Tom Murray

    thomasm@cadence.com

    • 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