cl: compile time vs. run time: inf vs. -nan(ind)

Question

Sample code (t50.c):

#include <stdio.h>
#include <stdint.h>
#include <inttypes.h>
#include <math.h>
#include <float.h>
#include <assert.h>

const float d1 = NAN;
const float d2 = -0x0p+0;
const float d3 = NAN / -0x0p+0;

typedef union { uint32_t u; float d; } u_t;

int main(void)
{
        u_t u1;
        u_t u2;
        u_t u3;

        u1.d = *(volatile float*)&d1 / *(volatile float*)&d2;
        u2.d = d3;
        u3.d = d1 / d2;
        if ( u1.u != u2.u || u1.u != u3.u )
        {
                printf("error:\n");
                printf("u1 (run time)     %08"PRIx32" %.*e\n", u1.u, DECIMAL_DIG, u1.d);
                printf("u2 (compile time) %08"PRIx32" %.*e\n", u2.u, DECIMAL_DIG, u2.d);
                printf("u3                %08"PRIx32" %.*e\n", u3.u, DECIMAL_DIG, u3.d);
        }
        return 0;
}

Compiler invocation: cl t50.c /O1 /fp:precise && t50

Expected result: <nothing>

Actual result (same for cl x86 and cl x64):

error:
u1 (run time)     ffc00000 -nan(ind)
u2 (compile time) 7f800000 inf
u3                ffc00000 -nan(ind)

I've specified /fp:strict: cl t50.c /O1 /fp:strict && t50, but got:

t50.c(8): error C2099: initializer is not a constant
t50.c(10): error C2099: initializer is not a constant

cl version: 19.25.28611 for x86 and 19.25.28611 for x64.

Compare with gcc (10.2.0) and clang (11.0.0):

gcc t50.c -O2 && a.exe
<nothing>

clang t50.c -O2 && a.exe
<nothing>

Why? What I'm missing here? What the standard (C / IEEE) says?

UPD1:

1. Same result for if ( u1.d != u2.d || u1.d != u3.d ).
2. Same result w/o unions (i.e. using float u1, u2, u3).

UPD2:

1. compiler's NAN definition: Windows Kits\10\Include\10.0.18362.0\ucrt\corecrt_math.h: #define NAN ((float)(INFINITY * 0.0F)).
2. Output for u1.d = NAN; printf("NAN %08"PRIx32" %.*e\n", u1.u, DECIMAL_DIG, u1.d); (for both cl x86 and cl x64): NAN ffc00000 -nan(ind).

Answer 1

Why?

cl does not follow IEEE-754 concerning NAN.

What I'm missing here?

Assuming a compliant C compiler follows IEEE.

What the standard C says?

C is lax with specs in the NAN department. I'd rate the compiler as compliant, just a weak quality of implementation concerning NAN.

What the standard IEEE says?

Non-compliant.