public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/101826] GFORTRAN: Debug info missing DW_TAG_string_type for array of variable length string Date: Mon, 09 Aug 2021 13:00:20 +0000 [thread overview] Message-ID: <bug-101826-4-TXUG4GVl3c@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101826-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101826 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2021-08-09 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed on trunk. The DW_TAG_structure_type contains the DW_AT_string_type: <1><126>: Abbrev Number: 17 (DW_TAG_structure_type) <127> DW_AT_declaration : 1 <1><127>: Abbrev Number: 6 (DW_TAG_array_type) <128> DW_AT_type : <0x13a> <12c> DW_AT_sibling : <0x13a> <2><130>: Abbrev Number: 18 (DW_TAG_subrange_type) <131> DW_AT_type : <0x2f> <135> DW_AT_upper_bound : <0x115> <2><139>: Abbrev Number: 0 <1><13a>: Abbrev Number: 19 (DW_TAG_string_type) <13b> DW_AT_string_length: <0x108> so appearantly we leak some implementation detail into the DWARF? When debugging with gdb I see (gdb) s str_arr (arr1=<incomplete type>, _arr1=10) at t.f90:1 1 subroutine str_arr (arr1) (gdb) ptype arr1 type = Type End Type and the function looks like void str_arr (struct array01_character(kind=1) & restrict arr1, integer(kind=8) _arr1) thus the parametrized string is passed as a reference to a structure plus a separate length argument. character(kind=1)[0:D.3976][1:_arr1] * restrict arr1.0; ... arr1.0_23 = arr1_18(D)->data;
next prev parent reply other threads:[~2021-08-09 13:00 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-09 9:27 [Bug fortran/101826] New: " abdul.b.ijaz at intel dot com 2021-08-09 13:00 ` rguenth at gcc dot gnu.org [this message] 2021-08-09 13:20 ` [Bug fortran/101826] " abdul.b.ijaz at intel dot com
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-101826-4-TXUG4GVl3c@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).