DVT SystemVerilog IDE User Guide
Rev. 24.1.7, 9 April 2024

41.9.1 Using the PVerilog editor (Deprecated)

This functionality is deprecated. To work with preprocessed files using the PVerilog editor, add the following directive in the build configuration file:


Whenever you open a (p) or (g) file (from any view, or by jumping into it with a hyperlink) it gets opened using the PVerilog editor.

It's a multi-page editor which provides a convenient way to work with preprocessed/generated code. It has 3 tabs:

  • (p) - Shows the preprocessing file with syntax highlighting.

Hyperlink navigation options are available (Open Declaration, Show Usages, etc).

DVT detects the element under cursor by advanced analysis of the diff between the (p) and the (g) files, however in certain situations (for example in case of massive diffs) several hyperlink candidates might be available.

To see the full list, click on Show more....

From the pop-up dialog, choose the hyperlink navigation option and the element for which it should be applied.

  • (g) - Shows the generated code in a regular SystemVerilog editor. All of the advanced navigation and editing features of DVT are available (hyperlinks, autocomplete, errors as you type etc). Whenever you edit this file, a visual indicator reminds you that the file is generated.

  • Compare - A compare viewer of the (p) and (g) files. It is editable and allows you to move pieces of code between the two files. The (p) and (g) editors are synchronously scrolled.

A possible usage flow is to edit/debug code in the (g) tab of the PVerilog editor, and thus benefit from all the advanced DVT functionality. When done, quickly bring (p) and (g) files into sync using the compare viewer's "Copy from ..." buttons.