Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
This community is designed for sharing of public information. Please do not share Intel or third-party confidential information here.
27228 Discussions

Has anyone noticed any significant FP performance degradation with Ifort 2021?

Mark_Lewy
New Contributor III
334 Views

I've been doing some performance regression testing of Ifort 2021.3 against XE2019U5 and have noticed performance degradations of about 20-30% with my two real world test models with our simulation engine.  Minimal changes have been made to the solution to allow it to build with Ifort 2021.3 with VS 2019.

Profiling with VTune suggests some new Fortran RTL calls may be responsible: _for_ieee_signaling_lt_k8_ and _for_ieee_signaling_gt_k8_.

For example:

XE2019U5 - elapsed 109.756s, CPU 1608.253s

Ifort 2021.3 - elapsed 140.515s, CPU 2058.113s

  • _for_ieee_signaling_lt_k8_ - 118.048s
  • _for_ieee_signaling_gt_k8_ - 65.388s

My tests are being run on a Dell Precision 7540 with Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz 2.30 GHz.

 

0 Kudos
1 Solution
Mark_Lewy
New Contributor III
301 Views

I believe this is down to a new feature for IEEE signaling comparisons that is enabled by /standard-semantics, which we use, see https://software.intel.com/content/www/us/en/develop/documentation/fortran-compiler-oneapi-dev-guide...

 

To disable use /assume:noieee_compares

View solution in original post

3 Replies
andrew_4619
Honored Contributor I
329 Views

Are the options for run time checks the same in each case?  If they are you might find it interesting to switch some of those off and see if the difference does away.

Mark_Lewy
New Contributor III
315 Views

Hi Andrew,

I believe the run time check options are the same for both compilers.  I did add a suppression for W7762 for Ifort 2021, but don't believe it's significant.  Also, I changed the standards checking on one project from Fortran 2003 to 2008.

I wonder whether the default run time checks have changed though?

 

Mark_Lewy
New Contributor III
302 Views

I believe this is down to a new feature for IEEE signaling comparisons that is enabled by /standard-semantics, which we use, see https://software.intel.com/content/www/us/en/develop/documentation/fortran-compiler-oneapi-dev-guide...

 

To disable use /assume:noieee_compares

Reply