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

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

--- Comment #8 from sandra at gcc dot gnu.org ---
There is a workaround for this included in commit

93b6b2f614eb692d1d8126ec6cb946984a9d01d7

that doesn't fully solve the problem:  when "long double" and "float128" are
different types with the same storage size (as on x86_64), it assumes that size
maps onto the standard type "long double" instead of the GNU extension type.

Tobias is presently rewriting the front-end code to build CFI descriptors
directly instead of calling a library function, so as part of that change it
should be possible to properly capture the kind of the type as well as its
size.

  parent reply	other threads:[~2021-09-03  0:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04 20:05 [Bug fortran/100917] New: " jrfsousa at gcc dot gnu.org
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 [this message]
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-Awk05vI1T1@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).