cis2-conformance / vectors /matvec_v1.txt
aefinityAIINC's picture
CIS-2 v0.3b: spec, op-level conformance vectors, expected digests, GPU result
909e920 verified
Raw
History Blame Contribute Delete
1.34 kB
# CIS-2 conformance vector: matvec_v1
# op=matvec, spec ref: docs/CIS2_SPEC_v0.2.md §5.2 (Matvec), which in turn
# depends on §5.1 (strict left-to-right sequential dot product, `dot_seq`).
#
# Fields are `key=value`. `out_features`/`in_features` are plain decimal
# integers (small config constants, no float-parsing ambiguity).
# `w_bits` is `out_features * in_features` values, ROW-MAJOR (row `o`'s
# `in_features` entries first, then row `o+1`, ...), each a
# comma-separated `0x`-prefixed 32-bit hex IEEE-754 binary32 bit pattern
# (per tests/conformance/README.md's general convention). `x_bits` is
# `in_features` values, the shared input vector.
op=matvec
spec_ref=docs/CIS2_SPEC_v0.2.md#52-matvec-normative
out_features=3
in_features=3
# Row 0 is §5.1's own worked example, verbatim: w[0,:] = [1e8, 1.0, -1e8]
# dotted against x = [1,1,1] MUST give exactly 0.0_f32 (the `1.0` term is
# lost to rounding against the 1e8 partial sum) -- a conforming
# implementation MUST reproduce this exact cancellation, not just "close".
# Row 1 and row 2 use small exactly-representable values (no order
# sensitivity) as a plain-arithmetic sanity check alongside the
# order-sensitive row 0.
w_bits=0x4CBEBC20,0x3F800000,0xCCBEBC20,0x3F800000,0x40000000,0x40400000,0x3F000000,0xBFC00000,0x40800000
x_bits=0x3F800000,0x3F800000,0x3F800000