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/103054] [f18] Gfortran accepts invalid and rejects valid co_reduce argument keyword name
Date: Wed, 03 Nov 2021 13:42:57 +0000	[thread overview]
Message-ID: <bug-103054-4-pyoSOyMotC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103054-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103054

kargl at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kargl at gcc dot gnu.org

--- Comment #1 from kargl at gcc dot gnu.org ---
diff --git a/gcc/fortran/intrinsic.c b/gcc/fortran/intrinsic.c
index 219f04f2317..0e3dfd9e5e6 100644
--- a/gcc/fortran/intrinsic.c
+++ b/gcc/fortran/intrinsic.c
@@ -3805,7 +3805,7 @@ add_subroutines (void)
              BT_UNKNOWN, 0, GFC_STD_F2018,
              gfc_check_co_reduce, NULL, NULL,
              a, BT_REAL, dr, REQUIRED, INTENT_INOUT,
-             "operator", BT_INTEGER, di, REQUIRED, INTENT_IN,
+             "operation", BT_INTEGER, di, REQUIRED, INTENT_IN,
              result_image, BT_INTEGER, di, OPTIONAL, INTENT_IN,
              stat, BT_INTEGER, di, OPTIONAL, INTENT_OUT,
              errmsg, BT_CHARACTER, dc, OPTIONAL, INTENT_INOUT);

  reply	other threads:[~2021-11-03 13:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03  5:21 [Bug fortran/103054] New: " damian at sourceryinstitute dot org
2021-11-03 13:42 ` kargl at gcc dot gnu.org [this message]
2021-11-07  8:03 ` [Bug fortran/103054] " pinskia at gcc dot gnu.org
2021-11-07 15:46 ` jvdelisle2 at gmail dot com
2021-11-07 16:06 ` kargl at gcc dot gnu.org
2021-11-07 20:49 ` anlauf at gcc dot gnu.org
2021-11-07 22:43 ` tkoenig 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-103054-4-pyoSOyMotC@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).