From: Damian Rouson <damian@sourceryinstitute.org>
To: gfortran <fortran@gcc.gnu.org>,
"Vladimír Fuka" <vladimir.fuka@gmail.com>
Subject: Re: Bug 84894 - [F2018] provide iso_fortran_binding.h
Date: Tue, 20 Mar 2018 22:49:00 -0000 [thread overview]
Message-ID: <etPan.5ab1900a.6910a2b2.3745@sourceryinstitute.org> (raw)
In-Reply-To: <CAKe2itdrrrvEtP1+=NdpAwzgG4C0U3oQFKuX+vrzfrLq6OKiAg@mail.gmail.com>
On March 20, 2018 at 7:14:31 AM, Vladimír Fuka (vladimir.fuka@gmail.com) wrote:
> In my last fortran-dev install I see a file
> intall_dir/lib/gcc/x86_64-apple-darwin15.6.0/7.0.0/include/ISO_Fortran_binding.h
> I am attaching. Could you please check
Dominique,
is the header compatible with the current array descriptor for GCC8?
I assume it’s not compatible because the header file was written years ago and the new descriptors were communities on 25 January 2018. First, I’m hoping to just check whether MPICH will recognize it and progress to the next step so that I can ensure whether there is also another issue that crops up. Even if MPICH accepts the file and attempts to use it, I’m sure there will be many test failures because of the descriptor change and other forms of bit rot.
Damian
next prev parent reply other threads:[~2018-03-20 22:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 14:14 Vladimír Fuka
2018-03-20 22:49 ` Damian Rouson [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-16 10:31 Dominique d'Humières
2018-03-19 23:05 ` Damian Rouson
2018-03-20 15:13 ` Jeff Hammond
2018-03-15 23:46 Damian Rouson
2018-03-16 0:25 ` Steve Kargl
2018-03-16 0:43 ` Jeff Hammond
2018-03-16 1:50 ` Damian Rouson
2018-03-16 2:08 ` Steve Kargl
2018-03-16 2:46 ` Jeff Hammond
2018-03-16 2:54 ` Jeff Hammond
2018-03-16 4:31 ` Steve Kargl
2018-03-16 6:01 ` Jeff Hammond
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=etPan.5ab1900a.6910a2b2.3745@sourceryinstitute.org \
--to=damian@sourceryinstitute.org \
--cc=fortran@gcc.gnu.org \
--cc=vladimir.fuka@gmail.com \
/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).