Sorry for the late reply, I couldn't get back to this issue due to other priority work.
We’ve traced down floating point exception masks at the initialization of our project. We’ve found [exInvalidOp,exDenormalized,exZeroDivide,exOverflow,exUnderflow,exPrecision] this set of exceptions is already masked on our project.
For more confirmation we’ve created a new VCL application and traced down floating point exceptions. This time the set was [exDenormalized,exUnderflow,exPrecision].
Could you please tell us if there is any project setting or something that we can remove the ‘exZeroDivide’ exception from this set or get back to the default floating point exceptions?