Jump to content

kirloy

Members
  • Content Count

    9
  • Joined

  • Last visited

  1. For design using UVM from separate library -profiler_all must be used for asim command instead -profiler. -profiler collects data only for working library code. Other code in this case represents code from libraries other than work - in this case from UVM. When you use -profiler_all then code from all libraries used in simulation is profiled. If UVM needs to be profiled this is also good idea to use debug version of UVM (compile UVM with -dbg switch and use library created this way)
  2. Some issues with "other code" was fixed in newest Riviera 2015.10. Please try it.
  3. Have you tried to add uvm_resource_options::turn_off_auditing() before run_test. UVM collects lots of data which is not needed when you do not debug. In certain cases - when you have lots of uvm_resource data base accesses - then it can consume lots of memory. You design can start some activities later on during the tests which may slow down simulator - as it has much more to simulate - ie first test doeas all configuration and then it starts do some transission. Anyway profiler results should give you some clues you are just blind when not looking at it. ie you can run till the poi
×
×
  • Create New...