public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at charter dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/95647] operator(.eq.) and operator(==) treated differently
Date: Sun, 07 Feb 2021 16:35:22 +0000 [thread overview]
Message-ID: <bug-95647-4-Dc16tOmgIF@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
Jerry DeLisle <jvdelisle at charter dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jvdelisle at charter dot net
--- Comment #6 from Jerry DeLisle <jvdelisle at charter dot net> ---
(In reply to Bill Long from comment #5)
> Is this fixed in a release version of GCC?
Submitting patch for approval and will backport as the fix is simple. How far
back shall we go? 10 for sure. Eyeballing the time lines, it does not look like
9 will have any more releases. If someone knows otherwise, let me know.
next prev parent reply other threads:[~2021-02-07 16:35 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
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 [this message]
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-Dc16tOmgIF@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).