From: Tobias Burnus <burnus@net-b.de>
To: Janne Blomqvist <blomqvist.janne@gmail.com>
Cc: gcc patches <gcc-patches@gcc.gnu.org>, gfortran <fortran@gcc.gnu.org>
Subject: Re: [Patch, Fortran] PR55758 - Non-C_Bool handling with BIND(C)
Date: Tue, 26 Feb 2013 14:58:00 -0000 [thread overview]
Message-ID: <512CCD7D.3060400@net-b.de> (raw)
In-Reply-To: <CAO9iq9HM5CXDE4m29h84zphXq_sK01Jki7ruD9kc-2zmGtbNLQ@mail.gmail.com>
On January 10, 2013 20:42, Janne Blomqvist wrote:
> On Wed, Jan 9, 2013 at 12:34 AM, Tobias Burnus <burnus@net-b.de> wrote:
>> Janne Blomqvist worte:
>>> On Sun, Jan 6, 2013 at 6:52 PM, Tobias Burnus<burnus@net-b.de> wrote:
[Patch, which handles BIND(C) LOGICALs as integers, doing the necessary
casts to true logicals with TYPE_PRECISION() == 1.
http://gcc.gnu.org/ml/fortran/2013-01/msg00049.html ]
[...]
> Ah, thanks for the clarification. I think if we cannot make it really bullet-proof, then it's safer to reject it outright. Do you happen to know if anyone except openmpi would be affected? If only openmpi, then we could give them a nudge and the issue would
> likely be fixed by the time gcc 4.8 rolls out to end users.
I turns out that the current Message Passing Interface (MPI) 3.0
specification itself is affected (MPI03 module), which uses default-kind
LOGICAL (and default-kind INTEGER) with BIND(C) throughout the
specification. See http://lists.mpi-forum.org/mpi-comments/2013/02/0076.php
It is still unclear how the MPI committee will handle it.
(Unsurprisingly as the issue is only known since
Tobias
next prev parent reply other threads:[~2013-02-26 14:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 22:31 Tobias Burnus
2012-12-29 22:11 ` Janne Blomqvist
2012-12-30 10:42 ` Tobias Burnus
2013-01-06 16:52 ` Tobias Burnus
2013-01-06 18:31 ` Steve Kargl
2013-01-08 20:07 ` Janne Blomqvist
2013-01-08 22:34 ` Tobias Burnus
2013-01-10 19:42 ` Janne Blomqvist
2013-02-26 14:58 ` Tobias Burnus [this message]
2013-01-09 16:22 ` Tobias Burnus
2013-01-09 17:23 ` Mikael Morin
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=512CCD7D.3060400@net-b.de \
--to=burnus@net-b.de \
--cc=blomqvist.janne@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@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).