Labels

• area: assertions

  Issue involves assertions
• area: configure/compiling

  Issue involves configuring or compilating Verilator itself
• area: coverage

  Issue involves coverage generation
• area: data-types

  Issue involves data-types
• area: documentation

  Issue involves documentation
• area: elaboration

  Issue involves elaboration phase
• area: invoking/options

  Issue involves options passed to Verilator
• area: lint

  Issue involves SystemVerilog lint checking
• area: parser

  Issue involves SystemVerilog parsing
• area: performance

  Issue involves performance issues
• area: portability

  Issue involves operating system/compiler portability
• area: randomization

  Issue involves randomization/constraints
• area: scheduling

  Issue involves scheduling/ordering of events
• area: tests

  Issue involves the testing system
• area: tracing

  Issue involves tracing
• area: usability

  Issue involves general usability
• area: vpi/dpi/api

  Issue involves VPI, DPI, or verilated.h interface API
• area: wrong runtime result

  Issue involves an incorrect runtine result from Verilated model
• dependencies

  Pull requests that update a dependency file
• effort: days

  Expect this issue to require roughly days of invested effort to resolve
• effort: hours

  Expect this issue to require roughly hours of invested effort to resolve
• effort: minutes

  Expect this issue to require less than an hour of invested effort to resolve
• effort: weeks

  Expect this issue to require weeks or more of invested effort to resolve
• github_actions

  Pull requests that update GitHub Actions code
• good first issue

  Good for newcomers
• help wanted

  Extra attention is needed
• new

  New issue not seen by maintainers
• pr: dev-coverage

  Run Code coverage workflow on PR
• pr: rtlmeter

  Run RTLMeter workflow on PR
• resolution: abandoned

  Closed; not enough information or otherwise never finished