From: Harald Anlauf <anlauf@gmx.de>
To: fortran <fortran@gcc.gnu.org>, sgk@troutmask.apl.washington.edu
Subject: typespec in forall and implied-do
Date: Sun, 20 Nov 2022 22:28:40 +0100 [thread overview]
Message-ID: <trinity-592b5772-1d2d-4e13-8f57-8259676682c4-1668979720632@3c-app-gmx-bs70> (raw)
Steve,
for unknown reasons I cannot reply to your mail on gmane,
so trying directly via mailing list.
I tried your patch, and it works on the supplied testcases.
However, there is a scoping issue for the declaration of the
index variable, as can be seen by the following variation:
program foo
use iso_fortran_env, only : k => real_kinds
implicit none
integer, parameter :: n = size(k)
integer(8) :: i
!!$ integer, parameter :: &
!!$ & p(n) = [(precision(real(1.,k(i))), integer :: i = 1, n)]
integer, parameter :: &
& q(n) = [(kind(i), integer(2) :: i = 1, n)]
integer, parameter :: &
& r(n) = [(storage_size(i), integer(1) :: i = 1, n)]
!!$ print *, p
print *, q
print *, r
end program foo
After your patch, gfortran prints:
8 8 8 8
64 64 64 64
This suggests that the integer kind is taken from the host decl,
which is kind=8, and not the local one (2 or 1).
Crayftn (which chokes on your original testcase):
3*2
3*8
This is what I expect.
Intel doesn't accept storage_size() here, which is a bug.
Commenting the uses of array r, I then get:
2 2 2
At least this agrees with Cray.
Can you have another look at this?
Thanks so far for you patch!
Harald
next reply other threads:[~2022-11-20 21:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 21:28 Harald Anlauf [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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
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
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=trinity-592b5772-1d2d-4e13-8f57-8259676682c4-1668979720632@3c-app-gmx-bs70 \
--to=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=sgk@troutmask.apl.washington.edu \
/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).