• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

stillwater-sc / universal / 41557127986
89%
master: 84%

Build:
Build:
LAST BUILD BRANCH: fix/fixpnt-quire-resolve-saturates
DEFAULT BRANCH: master
Ran 03 Nov 2026 01:27AM UTC
Jobs 1
Files 773
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

03 Nov 2026 01:03AM UTC coverage: 88.486% (-0.005%) from 88.491%
41557127986

push

github

web-flow
fix(cfloat): describe the fp8 aliases as what they are, not OCP (#1905)

fp8e4m3 and fp8e5m2 enable max-exponent values, so they are not the OCP OFP8 formats (maxpos 416 vs 448 and 81920 vs 57344, inf and NaN at other encodings), yet type_tag printed "OFP 8-bit", the alias comment did not say so, and docs/number-systems/cfloat.md listed the fp8 aliases with hasMaxExpValues = false as "NVIDIA FP8" (and duble/quad with uint32_t blocks). Configurations are unchanged.

- type_tag prints "fp8eXmY (8-bit eXmY, max-exponent values)" for all four fp8 aliases.
- The alias comment says they are not OCP and names the encoding-identical types: microfloat e4m3 (NONSAT, overflow to NaN) and e5m2, cfloat<8,4,uint8_t,true,true,true> (E4M3 with SAT overflow) and cfloat<8,5,uint8_t,true,false,false> (E5M2, overflow to inf). Each checked on all 256 encodings.
- The docs record why OCP E4M3 reclaims 7 of its 8 top-binade encodings while E5M2 keeps the IEEE layout (FP16 interchange, little gain on 32 binades, inf/NaN for loss-scale overflow detection), per Micikevicius et al. 2022, next to the cfloat hasMaxExpValues choice.
- The docs list the header's configurations, the fp8 aliases in their own section with an OCP comparison including both OCP overflow modes.

Resolves #1903

BEHAVIOUR-CHANGE: type_tag of cfloat fp8e2m5/fp8e3m4/fp8e4m3/fp8e5m2 prints "(8-bit eXmY, max-exponent values)" instead of "(DL 8-bit ...)" / "(OFP 8-bit ...)"

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

4 of 4 new or added lines in 1 file covered. (100.0%)

3 existing lines in 1 file now uncovered.

56124 of 63427 relevant lines covered (88.49%)

8951115.39 hits per line

Coverage Regressions

Lines Coverage ∆ File
3
91.45
-2.56% include/sw/universal/verification/correctly_rounded_reference.hpp
Jobs
ID Job ID Ran Files Coverage
1 41557127986.1 03 Nov 2026 01:27AM UTC 773
88.49
GitHub Action Run
Source Files on build 41557127986
  • Tree
  • List 773
  • Changed 2
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #41557127986
  • eb881604 on github
  • Prev Build on main (#41519197556)
  • Next Build on main (#41669118951)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc