From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Steve Kargl via Fortran <fortran@gcc.gnu.org>
Subject: Re: typespec in forall and implied-do
Date: Wed, 16 Nov 2022 10:20:48 -0800 [thread overview]
Message-ID: <Y3UqAGqDckxZqUkZ@troutmask.apl.washington.edu> (raw)
In-Reply-To: <Y3Q5L4+MhAitbvUI@troutmask.apl.washington.edu>
On Tue, Nov 15, 2022 at 05:13:19PM -0800, Steve Kargl via Fortran wrote:
>
> This patch allows the above to compile and execute.
> It has only had some light testing, and I do not know
> if nested forall and implied-do loops do work. Feel
> free to commit as I cannot.
>
Appears to work for nested forall (at least in the execution
part of a subprogram).
! From Section 6.9 of MR&C
program foo
implicit none
integer, parameter :: n = 9
integer i, j
integer k
integer a(n,n), b(n,n)
a = reshape([(i,i=1,n**2)], [n,n])
do k = 1, 9
print '(*(I3))', a(k,:)
end do
print *
b = a
forall (i = 1:n-1)
forall (j = i+1:n)
a(i,j) = a(j,i) ! a is a rank-2 array
end forall
end forall
do k = 1, 9
print '(*(I3))', a(k,:)
end do
print *
a = b
forall (integer :: ii = 1:n-1)
forall (integer :: jj = ii+1:n)
a(ii,jj) = a(jj,ii) ! a is a rank-2 array
end forall
end forall
do k = 1, 9
print '(*(I3))', a(k,:)
end do
print *
end program foo
--
Steve
next prev parent reply other threads:[~2022-11-16 18:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 1:13 Steve Kargl
2022-11-16 2:31 ` Steve Kargl
2022-11-16 20:24 ` Steve Kargl
2022-11-16 18:08 ` Steve Kargl
2022-11-16 18:20 ` Steve Kargl [this message]
2022-11-16 21:30 ` Steve Kargl
2022-11-17 0:32 ` Steve Kargl
2022-11-17 0:47 ` Steve Kargl
2022-11-17 4:15 ` Steve Kargl
2022-11-17 18:48 ` Steve Kargl
2022-11-20 21:28 Harald Anlauf
2022-11-20 23:31 ` Steve Kargl
[not found] ` <d2efcc09-f5be-904e-fb70-f75fdabbee1f@orange.fr>
[not found] ` <Y3vHlojilLVU8qC2@troutmask.apl.washington.edu>
2022-11-27 19:17 ` Mikael Morin
2022-11-27 19:33 ` Mikael Morin
2022-11-20 23:33 ` Steve Kargl
2022-11-22 21:15 ` Harald Anlauf
2022-11-22 21:59 ` Steve Kargl
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=Y3UqAGqDckxZqUkZ@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=fortran@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).