public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Janne Blomqvist <blomqvist.janne@gmail.com>
To: Tobias Burnus <burnus@net-b.de>
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: Sat, 29 Dec 2012 22:11:00 -0000	[thread overview]
Message-ID: <CAO9iq9HG-VhX-_7yUpg0mPjEzvRmp=ZB6bKVPQ9qtP+Yjf==_Q@mail.gmail.com> (raw)
In-Reply-To: <50DCCC29.6010206@net-b.de>

On Fri, Dec 28, 2012 at 12:31 AM, Tobias Burnus <burnus@net-b.de> wrote:
> Dear all,
>
> See also the discussion in the thread starting at
> http://gcc.gnu.org/ml/fortran/2012-12/msg00135.html
>
> a) The Fortran standard only defines LOGICAL(kind=C_Bool) as being
> interoperable with C - no other LOGICAL type. That matches GCC: With gcc
> (the C compiler) only _Bool is a BOOLEAN_TYPE with TYPE_PRECISION == 1.
> Hence, this patch rejects other logical kinds as dummy argument/result
> variable in BIND(C) procedures if -std=f2003/f2008/f2008ts is specified
> (using -pedantic, one gets a warning).

Sorry, I don't understand, what is the -pedantic warning about if it's
already rejected? Or do you mean std=gnu -pedantic?

> b) As GNU extension, other logical kinds are accepted in BIND(C) procedures;
> however, as the main use of "LOGICAL(kind=4)" (for BIND(C) procedures) is to
> handle logical expressions which use C's int, one has to deal with all
> integer values and not only 0 and 1. Hence, a normal integer type is used
> internally in that case. That has been done to avoid surprises of users and
> hard to trace bugs.

Does this actually work robustly? E.g. if you have a logical but
really integer under the covers, what happens if you equivalence it
with a "normal" logical variable. Or pass it as an argument to a
procedure expecting a normal logical etc. I suspect this might be
opening a can of worms..


-- 
Janne Blomqvist

  reply	other threads:[~2012-12-29 22:11 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 [this message]
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
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='CAO9iq9HG-VhX-_7yUpg0mPjEzvRmp=ZB6bKVPQ9qtP+Yjf==_Q@mail.gmail.com' \
    --to=blomqvist.janne@gmail.com \
    --cc=burnus@net-b.de \
    --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).