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/96255] [F2018] Implement optional type spec for index in DO CONCURRENT
Date: Tue, 21 Jul 2020 05:57:32 +0000	[thread overview]
Message-ID: <bug-96255-4-yzF3kBmyQ4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96255-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from kargl at gcc dot gnu.org ---
(In reply to kargl from comment #2)
> This issue depends on the fix for FORALL.  In gfc_match_do in the concurrent
> section, one gets to 
> 
>       m = match_forall_header (&head, &mask);
> 
> to match the control portion of the statement.

This should be trivial for a new gfortran contributor.  In
match.c(match_forall_header) prior to line 2401

  m = match_forall_iterator (&new_iter);

one needs to essentially copy lines 1229-1259 from array.c
and modify the checks to enforce an integer type.

  parent reply	other threads:[~2020-07-21  5:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21  0:47 [Bug fortran/96255] New: [F2018] Implement option type spec for index " jvdelisle at charter dot net
2020-07-21  4:24 ` [Bug fortran/96255] [F2018] Implement optional type spec for index in " kargl at gcc dot gnu.org
2020-07-21  5:53 ` kargl at gcc dot gnu.org
2020-07-21  5:57 ` kargl at gcc dot gnu.org [this message]
2020-07-21 14:34 ` dominiq at lps dot ens.fr
2020-07-21 19:41 ` jvdelisle at charter dot net
2020-07-21 19:44 ` jvdelisle at charter dot net
2020-07-21 20:25 ` sgk at troutmask dot apl.washington.edu
2020-07-22  6:29 ` kargl at gcc dot gnu.org
2020-07-22 18:25 ` kargl at gcc dot gnu.org
2021-11-11 21:01 ` anlauf at gcc dot gnu.org
2023-02-02 20:11 ` Boyce at engineer dot com
2023-02-03  7:25 ` kargl 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-96255-4-yzF3kBmyQ4@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).