public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug ada/28115] Support packed array encoded as DW_TAG_subrange_type Date: Tue, 07 Sep 2021 09:42:12 +0000 [thread overview] Message-ID: <bug-28115-4717-HHv5upVHqL@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28115-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28115 --- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> --- Hmm, this recent gcc commit looks interesting: ... commit c0b03afeab4502da3040ef1ebbd28f826737fa8a Author: Eric Botcazou <ebotcazou@adacore.com> Date: Mon Sep 6 11:16:08 2021 +0200 Fix debug info for packed array types in Ada Packed array types are sometimes represented with integer types under the hood in Ada, but we nevertheless need to emit them as array types in the debug info so we have the types.get_array_descr_info langhook for this purpose; but it is not invoked from modified_type_die, which causes: FAIL: gdb.ada/arrayptr.exp: scenario=minimal: print pa_ptr.all FAIL: gdb.ada/arrayptr.exp: scenario=minimal: print pa_ptr.all(3) in the GDB testsuite. gcc/ * dwarf2out.c (modified_type_die): Deal with all array types earlier and use local variable consistently throughout the function. ... -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-09-07 9:42 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-21 10:13 [Bug ada/28115] New: " vries at gcc dot gnu.org 2021-07-21 12:19 ` [Bug ada/28115] " cvs-commit at gcc dot gnu.org 2021-07-21 12:22 ` cvs-commit at gcc dot gnu.org 2021-09-07 9:42 ` vries at gcc dot gnu.org [this message] 2022-02-28 20:33 ` tromey at sourceware dot org 2022-02-28 20:44 ` tromey at sourceware dot org 2022-03-07 14:57 ` cvs-commit at gcc dot gnu.org 2022-03-07 14:58 ` tromey at sourceware dot 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-28115-4717-HHv5upVHqL@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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).