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
{{ message }}
Repository navigation
det runtime: a result overflowing a binary receiver's bytes (no ON SIZE ERROR) is stored unlike GnuCOBOL #4684
An arithmetic result too large for a binary receiver's bytes, with no ON SIZE ERROR, is stored differently by the det runtime and by GnuCOBOL 3.1.2 (-std=ibm, the oracle):
cobc: 1.24800, det port: 4.69440 (the unsigned 2-byte receiver gets -98775 at scale 4). The same happens for a left-P binary receiver (PIC VP9(4) COMP: cobc 0.59264, det 0.10688). Not P-specific: found by the P-scaled fuzz of #4669 / #4670 as the one remaining difference, reproduced with the unscaled PICTURE. Possibly the same family as the size-error / store guards of #4655. Acceptance: modelled as cobc stores it (and as IBM would, or declared), or refused by name; a test pins it.
Activity
det gen: cb_fits_int's literal exponent typed for mypy (#4684)
det runtime: a lifted COMP-5 item keeps its bytes under TRUNC(STD) (#…
det runtime: an unsigned binary ADD / SUBTRACT stores IBM's absolute …
det: an unsigned binary ADD / SUBTRACT wraps as cobc's native arithme…
port_blockers: 12 closed det/harness blockers from #4684-#6065 (Part of