You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The bytecode emitter errors out if you try to use a return type like xN[RESULT_SIGNED][RESULT_SZ].
: INVALID_ARGUMENT: Provided status is not in recognized error form: INTERNAL: Bits-to-array cast bit counts must match. Saw 32 vs 0.; while evaluating: to_int<u32:8, u32:23, u32:32>(APFloat<u32:8, u32:23> { sign: u1:0, bexp: u8:0x0, fraction: u23:0x0 })
...
Error: INTERNAL: Bits-to-array cast bit counts must match. Saw 32 vs 0.; while evaluating: ...
=== Source Location Trace: ===
To Reproduce
Steps to reproduce the behavior:
Change this line:
@proppy suggested this undocumented feature, pointing to 9761efb.
Once fixed, it would also be good to document it at https://google.github.io/xls/dslx_reference/#bit-type. xN is referenced in a couple places, but it's not clear this is not just a convenience shorthand for documentation.
Describe the bug
The bytecode emitter errors out if you try to use a return type like
xN[RESULT_SIGNED][RESULT_SZ]
.To Reproduce
Steps to reproduce the behavior:
Change this line:
xls/xls/dslx/stdlib/apfloat.x
Line 1301 in 69f00f9
to
xN[RESULT_SIGNED][RESULT_SZ]
(updating the casts atxls/xls/dslx/stdlib/apfloat.x
Line 1352 in 69f00f9
xls/xls/dslx/stdlib/apfloat.x
Line 1355 in 69f00f9
Expected behavior
This should properly include parameterized signedness and remove the need to cast the result in the wrapper at
xls/xls/dslx/stdlib/apfloat.x
Line 1370 in 69f00f9
The text was updated successfully, but these errors were encountered: