From: Thomas Koenig <tkoenig@netcologne.de>
To: Toon Moene <toon@moene.org>, sgk@troutmask.apl.washington.edu
Cc: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: Bug in closed-source, proprietary software that I do not have access to
Date: Sat, 25 May 2019 17:31:00 -0000 [thread overview]
Message-ID: <1332af12-1488-9ac1-c0d2-c655277f67df@netcologne.de> (raw)
In-Reply-To: <7a60f1f7-a682-ff97-ad15-0eca763646fc@moene.org>
Hi Toon,
> On 5/25/19 7:01 PM, Steve Kargl wrote:
>
>> For WRF, I suppose you or Martin could be a good citizen and
>> contact the project to report a bug.
>
> I have thought about this. As a person with experience building and
> running weather forecasting codes, I would be first in line to try this.
> But the SPEC code could be modified and not resemble a fresh WRF setup ...
The current version of netcdf has, in module_netcdf_nf_interfaces.F90,
!--------------------------------- nf_put_vara_double ----------------------
Interface
Function nf_put_vara_double(ncid, varid, start, counts, dvals) &
RESULT(status)
USE netcdf_nf_data, ONLY: RK8
Integer, Intent(IN) :: ncid, varid
Integer, Intent(IN) :: start(*), counts(*)
Real(RK8), Intent(IN) :: dvals(*)
Integer :: status
End Function nf_put_vara_double
End Interface
which looks good (well, it's not BIND(C)). In another file,
it has it as a simple INTEGER declaration with EXTERNAL.
I don't know which of the two is actually used.
next prev parent reply other threads:[~2019-05-25 17:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-25 12:53 Thomas Koenig
2019-05-25 13:16 ` Toon Moene
2019-05-25 14:37 ` Thomas Koenig
2019-05-25 14:03 ` Richard Biener
2019-05-25 14:48 ` gilles
2019-05-25 17:20 ` Thomas Koenig
2019-05-25 17:01 ` Steve Kargl
2019-05-25 17:19 ` Toon Moene
2019-05-25 17:31 ` Thomas Koenig [this message]
2019-05-25 17:43 ` Toon Moene
2019-05-26 14:15 ` Toon Moene
2019-05-26 18:12 ` Thomas Koenig
2019-05-27 7:46 ` Martin Liška
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=1332af12-1488-9ac1-c0d2-c655277f67df@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=sgk@troutmask.apl.washington.edu \
--cc=toon@moene.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).