[Bug fortran/95647] operator(.eq.) and operator(==) treated differently
cvs-commit at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Fri Feb 12 21:05:28 GMT 2021
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95647
--- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jerry DeLisle
<jvdelisle@gcc.gnu.org>:
https://gcc.gnu.org/g:d5021162cf33081c128cd5c4f96ea0b7ca8739d7
commit r10-9365-gd5021162cf33081c128cd5c4f96ea0b7ca8739d7
Author: Steve Kargl <sgk@troutmask.apl.washington.edu>
Date: Fri Feb 12 13:04:14 2021 -0800
libgfortran: Fix PR95647 by changing the interfaces of operators .eq. and
.ne.
The FE converts the old school .eq. to ==,
and then tracks the ==. The module starts with == and so it does not
properly overload the .eq. Reversing the interfaces fixes this.
2021-02-12 Steve Kargl <sgk@troutmask.apl.washington.edu>
libgfortran/ChangeLog:
PR libfortran/95647
* ieee/ieee_arithmetic.F90: Flip interfaces of operators .eq. to
== and .ne. to /= .
gcc/testsuite/ChangeLog:
PR libfortran/95647
* gfortran.dg/ieee/ieee_12.f90: New test.
More information about the Gcc-bugs
mailing list