Profile identity remains part of exact compatibility: the legacy IEEE
exceptional policy does not specify target-independent NaN payload/default
bits. Different targets need a shared qualified profile, or stronger explicit
conformance evidence; matching operation names alone is insufficient.
145def numericalProfileBytes =
146 (lambda unrestricted profile : (family StdNumericProfile) .
147 (bytes-append
148 (stdNumericProfileIdentityBytes (stdNumericProfileIdentityOf profile))
149 (bytes-append
150 (stdNumericWord (stdNumericFormatCode (stdNumericProfileStorageOf profile)))
151 (bytes-append
152 (stdNumericWord (stdNumericFormatCode (stdNumericProfileAccumulationOf profile)))
153 (bytes-append
154 (stdNumericWord (numericalRoundingCode (stdNumericProfileRoundingOf profile)))
155 (bytes-append
156 (stdNumericWord (numericalContractionCode (stdNumericProfileContractionOf profile)))
157 (bytes-append
158 (stdNumericWord
159 (numericalReductionCode (stdNumericProfileReductionOrderOf profile)))
160 (bytes-append
161 (stdNumericWord (numericalSubnormalCode (stdNumericProfileSubnormalsOf profile)))
162 (bytes-append
163 (stdNumericWord
164 (numericalExceptionalCode (stdNumericProfileExceptionalOf profile)))
165 b"")))))))))The compiler supplied declaration spans and resolved links from this source snapshot. This page does not assert that this file belongs to a checked closure.