Please find below an issue (and reproducer) encountered by one of our development
I believe the error may be occurring during constant folding (constant evaluation) during compilation - that's why changing how the expression is evaluated works around. I'm not sure why -fpe0 triggers it. The good news is that this problem no longer occurs with the version 17.0.2 (2017 update 2) compiler that was posted to the Intel Registration Center last week. Please try that compiler on your larger application, and let us know if there are still any problems.