google / google/xls

reassociation pass is somewhat fragile about what concat/bitslice operations it can see through

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

Description

**Describe the bug**
The reassociation pass needs to be able to determine when operations are zero/sign extend operations in order to know if it can safely reassociate through these operations. It is somewhat fragile in how it does this meaning to get best results we need to run bitslice_simp and concat_simp before any use of reassocation. This is unfortunate and it would be better if reassociation could use an analysis more able to see through these operations.

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.