public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jrfsousa at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/100917] New: Bind(c): errors handling long double real
Date: Fri, 04 Jun 2021 20:05:38 +0000	[thread overview]
Message-ID: <bug-100917-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100917

            Bug ID: 100917
           Summary: Bind(c): errors handling long double real
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jrfsousa at gcc dot gnu.org
  Target Milestone: ---

Created attachment 50945
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50945&action=edit
Fortran code showing problem

Hi All!

Wrong type and kind on handling long double real. Since kind is not related to
elem_len there seems to be no way to infer it.

Seen on:

GNU Fortran (GCC) 10.3.1 20210526
GNU Fortran (GCC) 11.1.1 20210526
GNU Fortran (GCC) 12.0.0 20210529 (experimental)

Thank you very much.

Best regards,
José Rui

             reply	other threads:[~2021-06-04 20:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04 20:05 jrfsousa at gcc dot gnu.org [this message]
2021-06-04 20:05 ` [Bug fortran/100917] " jrfsousa at gcc dot gnu.org
2021-06-13 18:41 ` jrfsousa at gcc dot gnu.org
2021-06-13 18:42 ` jrfsousa at gcc dot gnu.org
2021-06-26 23:35 ` sandra at gcc dot gnu.org
2021-06-29  3:35 ` sandra at gcc dot gnu.org
2021-07-11 20:55 ` sandra at gcc dot gnu.org
2021-09-02 23:42 ` cvs-commit at gcc dot gnu.org
2021-09-03  0:04 ` sandra at gcc dot gnu.org
2021-10-22 16:33 ` sandra at gcc dot gnu.org

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=bug-100917-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).