<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div class="moz-cite-prefix">On 11/13/2026 16:48, RAJAN BHAKTA
wrote:<br>
</div>
<blockquote type="cite" cite="mid:BYAPR15MB2326282B591245505EBDA42B9C7F2@BYAPR15MB2326.namprd15.prod.outlook.com">
<div style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<b>1062</b>: Intent is to allow it if the implementation wants
(efficiency). (SNaNs cause exceptions on assignment?)</div>
<div style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Question 1: Implementation defined should still take
precedence. This is the most likely case due to efficiency. Most
implementations likely do byte-wise or chunk-wise copy on
hardware so it would be a burden to require tracking contents
and triggering the signal. Matches existing behaviour as well
for implementations that I know of.</div>
<div style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Question 2: Like question 1. Most likely will be like a
trap representation. Signals should only occur only on a read,
not assignment.</div>
<div style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Question 3: No standard library function should produce a
SNaN other than ones that directly modify it (like setting
payloads). Uninitialized objects being a SNaN (Ex. malloc'd
storage) and then assigned should signal if a read is done just
like trap representations.</div>
</blockquote>
<p>The notes I wrote down for this case summarizes as follows:</p>
<p> This basically asks if struct/union copies are <code>memcpy</code>
or assign of individual struct fields according to the abstract
machine. I think the abstract machine leans to the latter, in
which case yeah, you can get FP exceptions. Note that you
definitely can get this on bare structs in function calls/returns.
Standard library functions probably can't produce sNaN except
under specific conditions. varargs can signal FP exceptions for
float args, although the exact place it gets signaled is :shrug:</p>
</body>
</html>