google / google/xls

Fuzz LEC flow

Open
#667 0 comments 0 reactions 0 assignees View on GitHub
formal fuzz
Dominant language
C++
Stars
1.9k
Forks
283
Avg merge
2d 10h
Merged PRs (30d)
135

Description

Our LEC flow has light usage and no fuzzing which means it probably has bitrotted some. To keep it fresh and bugfree we should fuzz it. Potential options of increasing complexity:

* prove unopt IR equivalent opt IR
* prove opt IR equivalent to parsed netlist (requires a backend flow such as openroad)
* do per-stage LEC'ing of a pipeline

An interesting issue with LEC is that it may timeout. This doesn't pose a fundamental problem as timeout can be considered a non-failing sample.

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.