public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rimvydas.jas at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/108056] backward compatibility issue between 11 and 12
Date: Sun, 11 Dec 2022 08:44:42 +0000 [thread overview]
Message-ID: <bug-108056-4-V5paczNJwy@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
Rimvydas (RJ) <rimvydas.jas at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rimvydas.jas at gmail dot com
--- Comment #4 from Rimvydas (RJ) <rimvydas.jas at gmail dot com> ---
$ gfortran11 -g -fno-backtrace pr108056.f90
$ ./a.out && echo works
works
<--copy executable to system with gcc-13 trunk-->
$ ./a.out
Internal Error: Invalid type in descriptor
$ gdb ./a.out
(gdb) b _gfortrani_internal_error
(gdb) b ISO_Fortran_binding.c:219
(gdb) r
_gfortran_gfc_desc_to_cfi_desc(d_ptr=0x7fffffffe948, s=0x7fffffffe970) at
/gcc_trunk/libgfortran/runtime/ISO_Fortran_binding.c:219
219 internal_error (NULL, "Invalid type in descriptor");
(gdb) where
#0 _gfortran_gfc_desc_to_cfi_desc (d_ptr=0x7fffffffe948, s=0x7fffffffe970) at
/gcc_trunk/libgfortran/runtime/ISO_Fortran_binding.c:219
#1 0x000055555555524b in pub_f08ts (a=<unknown type in /tmp/pr108056/a.out, CU
0x53d, DIE 0x5fe>, b=<unknown type in /tmp/pr108056/a.out, CU 0x53d, DIE
0x60b>) at pr108056.f90:29
#2 0x00005555555551f0 in bugsub (a=1, b=-3.08878791e-13) at pr108056.f90:35
#3 0x0000555555555313 in bug () at pr108056.f90:43
(gdb) p d->type
$1 = 11
(gdb) p type
$2 = 11 '\v'
(gdb) p *s
$3 = {base_addr = 0x7fffffffe9ec, offset = 0, dtype = {elem_len = 4, version =
0, rank = 0 '\000', type = 11 '\v', attribute = 2}, span = 4, dim =
0x7fffffffe998}
(gdb) p/d BT_ASSUMED
$4 = 11
/* NOTE: Since GCC 12, the FE generates code to do the conversion
directly without calling this function. */
void
gfc_desc_to_cfi_desc (CFI_cdesc_t **d_ptr, const gfc_array_void *s)
{
Looks to be backwards compatibility issue, BT_ASSUMED not handled?
next prev parent reply other threads:[~2022-12-11 8:44 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 [this message]
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
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-V5paczNJwy@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).