https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98577
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WONTFIX |INVALID
--- Comment #11 from kargl at gcc dot gnu.org ---
(In reply to Chinoune from comment #10)
> Intel Fortran 2021 reports the correct time:
>
> $ ifort -O3 bug_gcc_98577.f90 -o test.x
> $ ./test.x
> count_rate_r32: 1.219512
> count_rate_i32: 1.23957700000000
> count_rate_r64: 1.24717100000000
>
> $ ifx -O3 bug_count_rate.f90 -o test.x
> $ ./test.x
> count_rate_r32: 6.216970
> count_rate_i32: 6.89329900000000
> count_rate_r64: 6.90696400000000
>
> Thanks God, It is now available for free.
>
> Unlike the old time when gfortran was the only choice, we have now two other
> commercial compilers avialable for free (Intel and Nvidia) + the incoming
> LLVM/Flang.
Please stop. Gfortran does not have a bug. You are dividing
one processor-dependent value by another processor-dependent
value. The two processor-dependent values that you have asked
gfortran to return are incompatible. You have been told that
this behavior is documented, but you refuse to accept it.
Your above test shows only that Intel may have only *ONE* count_rate.
gfortran provides TWO count_rate values that allow both low and high
resolution timing.
