Skip to content

Releases: google/xls

v0.0.0-10371-gd0a7f95d1

Choose a tag to compare

Clean up includes in xls/examples.

PiperOrigin-RevId: 954953757

v0.0.0-10357-g4f6a4a2ac

Choose a tag to compare

Integrate LLVM at llvm/llvm-project@0220c07a9401

Updates LLVM usage to match
[0220c07a9401](https://github.com/llvm/llvm-project/commit/0220c07a9401)

PiperOrigin-RevId: 953598123

v0.0.0-10355-gcaa474e4c

Choose a tag to compare

[NFC] `const` BPA for VisibilityEstimator

PiperOrigin-RevId: 953113888

v0.0.0-10351-g88084eb4f

Choose a tag to compare

Clean up includes in xls/dslx/lsp.

PiperOrigin-RevId: 952358702

v0.0.0-10335-g9c1dd684c

Choose a tag to compare

[Explicit State Access] Guard state_read references in schedule_graph…

v0.0.0-10323-g5527b2c0b

Choose a tag to compare

Refactor builder channel and state element API to store errors on the…

v0.0.0-10303-gf677ff3a8

Choose a tag to compare

[opt] Rollback fix CanonicalizePass clamping until missing IsBits che…

v0.0.0-10298-g35706e2be

Choose a tag to compare

[Explicit State Access]  Support Decoupled Next in proc_state_narrowi…

v0.0.0-10278-gf5e88fd5f

Choose a tag to compare

[ir] Optimize bits_ops::LongestCommonPrefixMSB with word-based operat…

v0.0.0-10267-g611b39c75

Choose a tag to compare

[codegen] Explicitly narrow over-width array indices

We already do this in most cases as part of our clamping logic. However, if we've proven the actual value is in-bounds, we previously didn't remember to make this narrowing explicit, which makes some Verilog linters complain.

PiperOrigin-RevId: 947297793