google / google/xls

Mismatch between `max_trace_verbosity` and `vtrace_fmt!` codegen output

Open
#3,080 0 comments 0 reactions 0 assignees View on GitHub
bug verification
Dominant language
C++
Stars
1.9k
Forks
283
Avg merge
2d 10h
Merged PRs (30d)
135

Description

**Describe the bug**

Even though one can specify a high value for `"max_trace_verbosity` in the codegen options.
Only `vtrace_fmt!` that use log level `u32:0` are emited in SytemVerilog.

**To Reproduce**

I created a small example to reproduce the problem.
It is available on the following branch:
* https://github.com/antmicro/xls/tree/vtrace_fmt

Steps to reproduce the behavior:
1. Get the code of the example
2. execute `bazel build //xls/examples:vtrace_fmt_verilog`
3. obsrve that only a `$display("Verbosity level 0");` is avaliable in the generated verilog

**Expected behavior**
The verilog should also contain `$display("Verbosity level 10");` since `max_trace_verbosity` was set to `100` for the `//xls/examples:vtrace_fmt_verilog` target

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.