public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/95647] operator(.eq.) and operator(==) treated differently
Date: Thu, 11 Jun 2020 22:50:55 +0000 [thread overview]
Message-ID: <bug-95647-4-iI3cRk0Wes@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95647-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95647
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #2 from kargl at gcc dot gnu.org ---
Thanks for the testcase. gfortran converts the old school .eq. to ==,
and then tracks the ==. The module starts with == and so it does not
properly overload the .eq. This fixes the issue.
Index: libgfortran/ieee/ieee_arithmetic.F90
===================================================================
--- libgfortran/ieee/ieee_arithmetic.F90 (revision 280157)
+++ libgfortran/ieee/ieee_arithmetic.F90 (working copy)
@@ -77,15 +77,16 @@ module IEEE_ARITHMETIC
! Equality operators on the derived types
- interface operator (==)
+ ! Note, the FE overloads .eq. to == and .ne. to /=
+ interface operator (.eq.)
module procedure IEEE_CLASS_TYPE_EQ, IEEE_ROUND_TYPE_EQ
end interface
- public :: operator(==)
+ public :: operator(.eq.)
- interface operator (/=)
+ interface operator (.ne.)
module procedure IEEE_CLASS_TYPE_NE, IEEE_ROUND_TYPE_NE
end interface
- public :: operator (/=)
+ public :: operator (.ne.)
! IEEE_IS_FINITE
next prev parent reply other threads:[~2020-06-11 22:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 21:14 [Bug fortran/95647] New: " longb at cray dot com
2020-06-11 21:49 ` [Bug fortran/95647] " dominiq at lps dot ens.fr
2020-06-11 22:50 ` kargl at gcc dot gnu.org [this message]
2020-06-13 8:11 ` tkoenig at gcc dot gnu.org
2020-06-13 16:16 ` sgk at troutmask dot apl.washington.edu
2021-01-22 17:53 ` longb at cray dot com
2021-02-07 16:35 ` jvdelisle at charter dot net
2021-02-07 17:04 ` longb at cray dot com
2021-02-07 17:55 ` jvdelisle at charter dot net
2021-02-08 0:30 ` kargl at gcc dot gnu.org
2021-02-09 4:46 ` jvdelisle at charter dot net
2021-02-12 15:58 ` cvs-commit at gcc dot gnu.org
2021-02-12 21:05 ` cvs-commit at gcc dot gnu.org
2021-02-13 21:44 ` jvdelisle at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-95647-4-iI3cRk0Wes@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).