Are there any specific considerations for MSVC to avoid unexpected truncation during such conversion
I have a simple program with a
getDouble()
function returning a double value slightly above INT_MAX (2147483647). The program attempts to convert this value to an unsigned int using both direct and indirect casting.
When compiling and running this code on MSVC x86
, the direct cast truncates the double value to 2147483648 that's one more than INT_MAX. This is unexpected because the value should fit within the range of an unsigned int typically 32-bits on x86. Funny enough, this behavior is not observed on GCC which is another compiler.
I've checked the Microsoft documentation but haven't found a specific explanation for this truncation on x86.
Is this a known behavior of MSVC x86 for double to unsigned int conversions, especially when the double value is slightly above INT_MAX?2 Replies
Here is the code from the editor :
Are there any specific considerations for MSVC to avoid unexpected truncation during such conversions?
@Middleware & OS