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: Fri, 03 Feb 2023 07:25:37 +0000 [thread overview]
Message-ID: <bug-96255-4-l6eActLyz7@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
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #11 from kargl at gcc dot gnu.org ---
(In reply to Scott Boyce from comment #10)
> Just wanted to see if there was any change on this. I just was about to post
> the same issue (and found this one) for compiling with 11.3.0 and 12.1.0 on
> Ubuntu.
>
> I used this feature all the time for routines that don't have any available
> integers and it seems silly to create an extra int at the top of a routine
> just for a loop index.
>
> Its also nice for keeping the variable isolated from the other parts of a
> routine, when its only purpose is to serve as a loop index.
As the audit trail shows the bug is almost fixed, but someone
needs to do the last little bit to finish it off. A workaround
would be to use a block construct. Instead of
do concurrent (integer :: i=1:10)
...
end do
you can do
block
integer i
do concurrent (integer :: i=1:10)
...
end do
end block
prev parent reply other threads:[~2023-02-03 7:25 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
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 [this message]
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-l6eActLyz7@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).