The UVM library evolves and while new features are added to its API, some other features are marked as deprecated. Using deprecated features is discouraged as they are supposed to be removed in future UVM versions. Sigasi marks all usages of deprecated API: macros, classes, methods, public fields, etc:
class my_sequence extends uvm_sequence #(my_sequence_item);
`uvm_object_utils(my_sequence)
function new(string name = "my_sequence");
super.new(name);
do_not_randomize = 1; // UVM declaration 'uvm_pkg::uvm_sequence_base::do_not_randomize' is deprecated
endfunction
task body();
`uvm_do_with(req, {req.size < 32;}) // UVM macro 'uvm_do_with' is deprecated
endtask
endclassBy default, API features deprecated in the UVM library version you are using are reported. However, it’s possible to configure the rule to report features deprecated in future UVM versions as well.
Rule configuration
This rule can be disabled for your project, or its severity and parameters can be modified in the project linting settings. Alternatively, it can be manually configured using one of the following templates, depending on the type of project you use.
For Modular Projects, add these entries to your project's
.sigasi/settings.jsonsettings file. To scope the settings to a specific folder or file instead of the whole project, place them inside an@overrideblock; to scope them to a specific target, place them inside a@targetsblock.JSONC{ "verilog.rules.152.severity": "{ERROR|WARNING|INFO|IGNORE}", "verilog.rules.152.parameters.up_to_version": "{CURRENT|UVM_1_2|UVM_2017|UVM_2020}" }For Classic Projects, add the VHDL lines to
.settings/com.sigasi.hdt.vhdl.linting.prefsand the Verilog/SystemVerilog lines to.settings/com.sigasi.hdt.verilog.linting.prefs:PREFS152/severity/${path}={error|warning|info|ignore} 152/params/up_to_version/${path}={CURRENT|UVM_1_2|UVM_2017|UVM_2020}