Releases: google/xls
Releases · google/xls
v0.0.0-5065-g6ef5c2a14
Documentation tests: include all markdowns that have dslx blocks Some of them commented out for now in the actual test, as they have issues that need to be addressed in a separate change. PiperOrigin-RevId: 631608573
v0.0.0-5060-gd94a1b0f7
Avoid using match in python code PiperOrigin-RevId: 631280405
v0.0.0-5050-g72961d5a8
Standardize cc_xls_ir_jit_wrapper class_names We would silently transform these into camel-case anyway. Make the class-name be camel case so we can stop doing this behavior and just take the class-name unchanged. This does not affect the generated code in any way. PiperOrigin-RevId: 630475745
v0.0.0-5044-ge4132f551
Don't include unused protocol buffer headers. Also: tell clang-tidy that poll.h is needed in subprocess.cc PiperOrigin-RevId: 630206678
v0.0.0-5041-gf4e0f594b
IWYU: Fix missing includes Addressing the top missing includes: * xls/ir/value.h * xls/ir/bits.h * xls/ir/node.h * xls/ir/source_location.h * absl/types/span.h Should fix at least around 1600 misc-include-cleaner warnings. PiperOrigin-RevId: 629910777
v0.0.0-5036-g52752f50b
Add an example for the intent of the scrub_crasher.cc PiperOrigin-RevId: 629559227
v0.0.0-5025-g51222db0e
Remove unnecessary dependencies in //xls/common:init_xls PiperOrigin-RevId: 629189443
v0.0.0-5018-ga3b4f4c6b
Avoid 'else' after return (clang-tidy readability-else-after-return) (fixes 27 of our clang-tidy warnings). While at it, fix a couple of includes. PiperOrigin-RevId: 628510900
v0.0.0-5007-g16831e939
Fix typo in comment. PiperOrigin-RevId: 628245992
v0.0.0-5005-gd8b09c68c
Fix bugs in `Interval::IsTrueWhenAndWith` This function's definition didn't quite meet its specification; in particular, it used an invalid mask. The result was incorrect behavior of all types (false positives & false negatives). This could have caused some incorrect optimization analyses for `PrioritySelect` in the RangeQueryEngine. Making an efficient implementation of this required the new `interval_ops::CoversTernary` function, which tests whether a ternary pattern intersects an `Interval` in O(bits) time. Since this function turned out to be quite complicated, I ended up writing a corresponding proof in the inline comments, and added fuzz testing (which quickly caught several bugs in my first implementation). I also exhaustively tested it for all combinations of 7-bit `Interval`s and 7-bit ternary patterns. (The exhaustive test took several minutes to run on my local machine, so I haven't checked that part in.) PiperOrigin-RevId: 627946453