new() v/s create

Question

Hi,

I am new to verification domain, specifically UVM testbench environments. I want to know the difference between new() and create (factory method). I know create method helps in factory overriding. If that's the case, why do we still use new() as the boiler plate constructor code for components?

Answer 1

Solution

yannlehenaff

Full Access

4 posts

July 26, 2022 at 10:07 am

You should always invoke create to create a component in the build phase. However, in the class declaration of your derived component, you will override the new constructor. The create function invokes the class constructor (new).

Answer 2

ABD_91

Forum Access

160 posts

July 28, 2022 at 8:41 am

In reply to Akhil Mehta:

Function create() would call the constructor new() within the UVM Base Class Library.
Hence user needs to provide constructor implementation .

At the end of the day , classes ( Objects / Components ) are instantiated using new() always .

Answer 3

dave_59

Forum Moderator

10500 posts

July 28, 2022 at 3:55 pm

In reply to Akhil Mehta:

Every class that is registered with the factory should be constructed using the create() method. You should look at this topic on The UVM Factory.

Some UVM classes, like TLM ports/exports are not registered with the factory, you you must construct them by calling new().

— Dave Rich, Verification Architect, Siemens EDA

Languages & Standards

Methodologies

Techniques & Tools

Universal Verification Methodology (UVM)

Featured Courses

Additional Courses

Formal-Based Techniques

Analog/Mixed Signal

UVM Forum

SystemVerilog Forum

Coverage Forum

Additional Forums

Implementation Patterns

Specification Patterns

Pattern Resources

UVM Cookbook

Coding Guidelines & Deployment

Coverage Cookbook

Featured & On-Demand

On-Demand Library

Recording Archive

Conferences & WRG

Siemens EDA Learning Center

Blog & News

Verification Horizons Publication

About Us

Training

Solution

Portfolio

Explore

Siemens

Contact