…vtsd2usi uses ulong.max_value to show FPE for negative, NAN and ulong_max + 1 values.

…architecture. This is because we have changed the JITDbl2Ulng helper function to mimic the new IEEE compliant AVX512 instruction vcvtsd2usi. In the process, we needed to update the library test case because the default Floating Point Error (FPE) value for the new instruction is different from the default MSVC FPE value i.e. 0.

…not changing the library test case but the API to make sure NaN cases are handled.

…id handling edge cases (-1,0) separately inside the helper.

…ulong/uint

trying to return EA_4BYTE for INS_vcvttss2usi to make sure that we read dword and not qword for float to ulong

… a special handling for vcvttss2usi64 to make sure we read only dword instead of qword for float to ulong conversion

…n for vcvttsd2usi, vcvttusi2sd32/64

…th other similar instructions

…r nowayasserts and also checking for float and doubel both in lowercast for overflow and conversion to ulong

…y are not available in release mode

…) into a single node i.e. GT_CAST(TYP_ULONG, TYP_FLOAT)

…ideration 32bit and 64 bit version of vcvttss2usi.

…endsOn only runs in debug mode.

…in asserts aka code review changes

…endsOn checks to make sure they are ran only if we need AVX512. These checks being costly, moving them to the innermost checks in nested if checks.

…-rebased