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/108056] [12/13 Regression] backward compatibility issue between 11 and 12 Date: Thu, 15 Dec 2022 11:27:31 +0000 [thread overview] Message-ID: <bug-108056-4-5Xm00pKkob@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108056-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108056 --- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tobias Burnus <burnus@gcc.gnu.org>: https://gcc.gnu.org/g:e205ec03f0794aeac3e8a89e947c12624d5a274e commit r13-4716-ge205ec03f0794aeac3e8a89e947c12624d5a274e Author: Tobias Burnus <tobias@codesourcery.com> Date: Thu Dec 15 12:25:07 2022 +0100 libgfortran's ISO_Fortran_binding.c: Use GCC11 version for backward-only code [PR108056] Since GCC 12, the conversion between the array descriptors formats - the internal (GFC) and the C binding one (CFI) - moved to the compiler itself such that the cfi_desc_to_gfc_desc/gfc_desc_to_cfi_desc functions are only used with older code (GCC 9 to 11). The newly added checks caused asserts as older code did not pass the proper values (e.g. real(4) as effective argument arrived as BT_ASSUME type as the effective type got lost inbetween). As proposed in the PR, revert to the GCC 11 version - known bugs is better than some fixes and new issues. Still, GCC 12 is much better in terms of TS29113 support and should really be used. This patch uses the current libgomp version of the GCC 11 branch, except it fixes the GFC version number (which is 0), uses calloc instead of malloc, and sets the lower bound to 1 instead of keeping it as is for CFI_attribute_other. libgfortran/ChangeLog: PR libfortran/108056 * runtime/ISO_Fortran_binding.c (cfi_desc_to_gfc_desc, gfc_desc_to_cfi_desc): Mostly revert to GCC 11 version for those backward-compatiblity-only functions.
next prev parent reply other threads:[~2022-12-15 11:27 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-11 6:37 [Bug libfortran/108056] New: " gilles.gouaillardet at gmail dot com 2022-12-11 7:05 ` [Bug libfortran/108056] " kargl at gcc dot gnu.org 2022-12-11 7:44 ` gilles.gouaillardet at gmail dot com 2022-12-11 7:51 ` gilles.gouaillardet at gmail dot com 2022-12-11 8:44 ` rimvydas.jas at gmail dot com 2022-12-11 13:19 ` [Bug libfortran/108056] [12/13 Regression] " rguenth at gcc dot gnu.org 2022-12-11 18:34 ` kargl at gcc dot gnu.org 2022-12-11 22:15 ` sandra at gcc dot gnu.org 2022-12-11 22:24 ` jakub at gcc dot gnu.org 2022-12-12 8:40 ` jakub at gcc dot gnu.org 2022-12-12 9:07 ` rguenther at suse dot de 2022-12-12 9:10 ` gilles.gouaillardet at gmail dot com 2022-12-12 12:09 ` burnus at gcc dot gnu.org 2022-12-12 12:34 ` rguenther at suse dot de 2022-12-15 11:27 ` cvs-commit at gcc dot gnu.org [this message] 2022-12-16 2:47 ` haochen.jiang at intel dot com 2022-12-16 7:48 ` burnus at gcc dot gnu.org 2022-12-16 7:57 ` cvs-commit at gcc dot gnu.org 2022-12-20 17:22 ` jakub at gcc dot gnu.org 2022-12-21 7:13 ` [Bug libfortran/108056] [12 " rguenth at gcc dot gnu.org 2022-12-21 7:23 ` cvs-commit at gcc dot gnu.org 2022-12-21 7:34 ` rguenth 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-108056-4-5Xm00pKkob@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).