public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/101305] Bind(C): Problems with incorrect kinds/sizes in ISO_Fortran_binding.h and CFI_establish Date: Wed, 28 Jul 2021 04:24:46 +0000 [thread overview] Message-ID: <bug-101305-4-slhU6qKNQI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101305-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101305 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Sandra Loosemore <sandra@gcc.gnu.org>: https://gcc.gnu.org/g:fef67987cf502fe322e92ddce22eea7ac46b4d75 commit r12-2551-gfef67987cf502fe322e92ddce22eea7ac46b4d75 Author: Sandra Loosemore <sandra@codesourcery.com> Date: Thu Jul 8 08:21:20 2021 -0700 Bind(C): Fix type encodings in ISO_Fortran_binding.h ISO_Fortran_binding.h had many incorrect hardwired kind encodings in the definitions of the CFI_type_* macros. Additionally, not all targets support all the defined type encodings, and the Fortran standard requires those macros to have a negative value. This patch changes ISO_Fortran_binding.h to use sizeof instead of hard-coded sizes, and assembles it from fragments that reflect the set of types supported by the target. 2021-07-22 Sandra Loosemore <sandra@codesourcery.com> Tobias Burnus <tobias@codesourcery.com> libgfortran/ PR libfortran/101305 * ISO_Fortran_binding.h: Fix hard-coded sizes and split into... * ISO_Fortran_binding-1-tmpl.h: New file. * ISO_Fortran_binding-2-tmpl.h: New file. * ISO_Fortran_binding-3-tmpl.h: New file. * Makefile.am: Add rule for generating ISO_Fortran_binding.h. Adjust pathnames to that file. * Makefile.in: Regenerated. * mk-kinds-h.sh: New file. * runtime/ISO_Fortran_binding.c: Fix include path.
next prev parent reply other threads:[~2021-07-28 4:24 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-03 5:48 [Bug libfortran/101305] New: " sandra at gcc dot gnu.org 2021-07-06 20:11 ` [Bug libfortran/101305] " sandra at gcc dot gnu.org 2021-07-08 19:03 ` sandra at gcc dot gnu.org 2021-07-14 0:08 ` sandra at gcc dot gnu.org 2021-07-28 4:24 ` cvs-commit at gcc dot gnu.org [this message] 2021-07-28 4:24 ` cvs-commit at gcc dot gnu.org 2021-07-28 4:24 ` cvs-commit at gcc dot gnu.org 2021-07-28 20:21 ` sandra at gcc dot gnu.org 2021-08-09 10:36 ` cvs-commit at gcc dot gnu.org 2021-08-10 15:27 ` cvs-commit 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-101305-4-slhU6qKNQI@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: linkBe 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).