[CI][FIRRTL][LLHD] valgrind failures on nightly (GCC, asserts=ON, shared=OFF)
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 524
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 46
Description
https://github.com/llvm/circt/actions/runs/5068362199/jobs/9100587371
Failing tests:
```
Failed Tests (13):
CIRCT :: Dialect/FIRRTL/parse-basic.fir
CIRCT :: Dialect/LLHD/Simulator/sim_arbitrary_signal_size.mlir
CIRCT :: Dialect/LLHD/Simulator/sim_bit_precision_drives.mlir
CIRCT :: Dialect/LLHD/Simulator/sim_comb_concat.mlir
CIRCT :: Dialect/LLHD/Simulator/sim_formats.mlir
CIRCT :: Dialect/LLHD/Simulator/sim_hw_array_get_concat.mlir
CIRCT :: Dialect/LLHD/Simulator/sim_hw_bitcast.mlir
CIRCT :: Dialect/LLHD/Simulator/sim_hw_struct_extract_inject.mlir
CIRCT :: Dialect/LLHD/Simulator/sim_process.mlir
CIRCT :: Dialect/LLHD/Simulator/sim_reg.mlir
CIRCT :: Dialect/LLHD/Simulator/sim_shifts.mlir
CIRCT :: Dialect/LLHD/Simulator/sim_simple.mlir
CIRCT :: Dialect/LLHD/Simulator/sim_wait.mlir
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked GitHub Actions run and its Valgrind output for the nightly GCC, asserts=ON, shared=OFF configuration. Examine the listed FIRRTL and LLHD simulator tests to identify the common failure, then verify that the 13 failures pass without Valgrind errors in the same configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100