* [Patch, committed] Fortran's dump-parse-tree.c: Use '==' not '=' for '.eq.'.
@ 2020-11-30 14:24 Tobias Burnus
0 siblings, 0 replies; only message in thread
From: Tobias Burnus @ 2020-11-30 14:24 UTC (permalink / raw)
To: gcc-patches, fortran
[-- Attachment #1: Type: text/plain, Size: 397 bytes --]
I was a bit confused by the '=' (assignment?) in the dump; hence,
in line with /=, >= etc. it now is '==' for '==' or '.eq.'.
Committed as r11-5570-g2610c786f7496c5006bb68d6801ef7450bd231a9
Tobias
-----------------
Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München / Germany
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Alexander Walter
[-- Attachment #2: committed.diff --]
[-- Type: text/x-patch, Size: 753 bytes --]
commit 2610c786f7496c5006bb68d6801ef7450bd231a9
Author: Tobias Burnus <tobias@codesourcery.com>
Date: Mon Nov 30 15:19:39 2020 +0100
Fortran's dump-parse-tree.c: Use '==' not '=' for '.eq.'.
gcc/fortran/
* dump-parse-tree.c (show_expr): Use '==' not '=' for '.eq.'.
diff --git a/gcc/fortran/dump-parse-tree.c b/gcc/fortran/dump-parse-tree.c
index cab0fb2979f..1012b11fb98 100644
--- a/gcc/fortran/dump-parse-tree.c
+++ b/gcc/fortran/dump-parse-tree.c
@@ -647,9 +647,9 @@ show_expr (gfc_expr *p)
fputs ("NEQV ", dumpfile);
break;
case INTRINSIC_EQ:
case INTRINSIC_EQ_OS:
- fputs ("= ", dumpfile);
+ fputs ("== ", dumpfile);
break;
case INTRINSIC_NE:
case INTRINSIC_NE_OS:
fputs ("/= ", dumpfile);
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-11-30 14:25 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-11-30 14:24 [Patch, committed] Fortran's dump-parse-tree.c: Use '==' not '=' for '.eq.' Tobias Burnus
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).