public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/105501] The statement TYPE IS without a space is accepted
Date: Mon, 09 May 2022 19:36:55 +0000	[thread overview]
Message-ID: <bug-105501-4-uADkO4Tf7C@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105501-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>:

https://gcc.gnu.org/g:8c97f7fd2382aa77f36567207e949447db90a1fb

commit r13-216-g8c97f7fd2382aa77f36567207e949447db90a1fb
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Sun May 8 22:04:27 2022 +0200

    Fortran: check for non-optional spaces between adjacent keywords

    In free format, spaces between adjacent keywords are not optional except
    when a combination is explicitly listed (e.g. F2018: table 6.2).  The
    following combinations thus require separating blanks: CHANGE TEAM,
    ERROR STOP, EVENT POST, EVENT WAIT, FAIL IMAGE, FORM TEAM, SELECT RANK,
    SYNC ALL, SYNC IMAGES, SYNC MEMORY, SYNC TEAM, TYPE IS.

    gcc/fortran/ChangeLog:

            PR fortran/105501
            * match.cc (gfc_match_if): Adjust patterns used for matching.
            (gfc_match_select_rank): Likewise.
            * parse.cc (decode_statement): Likewise.

    gcc/testsuite/ChangeLog:

            PR fortran/105501
            * gfortran.dg/pr105501.f90: New test.

  parent reply	other threads:[~2022-05-09 19:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06  7:31 [Bug fortran/105501] New: " chilikin.k at gmail dot com
2022-05-06 20:34 ` [Bug fortran/105501] " anlauf at gcc dot gnu.org
2022-05-06 20:51 ` anlauf at gcc dot gnu.org
2022-05-08 20:18 ` anlauf at gcc dot gnu.org
2022-05-09 19:36 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-09 19:38 ` anlauf 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-105501-4-uADkO4Tf7C@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).