Eric Astor
Running the splitOptionsWithSpaces fix can break lines that include a location reference; e.g., ``` linkopts = [ "-Wl,--version-script=$(location script.lds)", ], ``` becomes ``` linkopts = [ "-Wl,--version-script=$(location", "script.lds)", ], ```...
init_LweSample currently doesn't actually initialize the values in a; we use array value-initialization syntax to fix this.
The fuzzer found the following IR: ``` package sample top fn __sample__main(x0: bits[22], x1: bits[1]) -> bits[52] { bit_slice.34: bits[1] = bit_slice(x0, start=0, width=1, id=34) one_hot.15: bits[2] = one_hot(bit_slice.34, lsb_prio=true,...
Found using the XLS fuzzer over the weekend (~Mar 2) With `test.ir`: ``` package subrosa top fn function_0(param: bits[40], param__1: bits[20]) -> (bits[1], bits[40]) { literal.3: bits[40] = literal(value=549755813889, id=3)...
### What's hard to do? (limit 100 words) Currently, priority-select always uses a zero default value, restricting its use to Bits-typed inputs. ### Current best alternative workaround (limit 100 words)...
### What's hard to do? (limit 100 words) If we're writing code in DSLX, it's difficult to tell at a glance which code may contain timing-sensitive operations - and thus...
### What's hard to do? (limit 100 words) Accept values from "configuration registers" and reference them in your circuit. These are values that can be assumed not to change between...
This operation is not present in XLS docs, but does exist in XLS IR.
**Describe the bug** `eval_ir_main` produces different results for the following IR with the interpreter and the JIT: ``` package sample top fn __sample__main(x0: bits[28] id=1) -> ((bits[1], bits[17]), bits[51]) {...
Appears to be a JIT issue, and only manifests at LLVM opt-level 3 (LLVM opt-level 2 stops the problem). The issue seems to be difficult to minimize, the minimized IR...