Chris Leary

Failures: ``` $ bazel test -c opt --keep_going -- //xls/... -//xls/contrib/... |& tee /tmp/output.txt [snip] FAILED: Build did NOT complete successfully //xls/build_rules/tests:__add_one_combinational_rtl FAILED TO BUILD //xls/build_rules/tests:__add_one_dslx_verilog FAILED TO BUILD //xls/build_rules/tests:__add_one_pipeline_rtl...

Thanks for the pointer @proppy ! I'll try to do the dependency bump dance in a bit here and see how it goes.

Just an update here, I have a release branch with builds for both x86_64 and arm64 on OS X here: https://github.com/xlsynth/xlsynth/releases/tag/v0.0.87 So far it's been easy enough to do the...

I think this need a rebase to merge, thanks.

@Cmsonger I thought "block" as @meheff had it in his original post sounded good. Procs are blocks with the ability to stall and plan out the FSM/pipeline (which I tended...

@mikex-oss A nit, maybe not a deep distinction but seemed worth mentioning -- it's a warning (collected by the warning collector) and we have warnings-as-errors on by default, which is...

@mikex-oss I was trying to avoid naming it directly, but I do believe warnings-as-errors is the default policy in g3, which is where this "why on by default" stemmed from...

Leaving out early returns (historically) was intentional -- we chatted about this largely in lunch conversations and similar. The challenge is that in a software programming language early returns are...

Note we also tried passing `--help` to the `%%dslx` magic but that didn't spit out help info.

If we're not going to add an IR node for it (and I don't think we have any active plans to) I think we should probably remove this in favor...