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/26903] FAIL: gdb.ada/array_of_variant.exp: scenario=minimal: print entire array
Date: Mon, 26 Jul 2021 10:36:13 +0000 [thread overview]
Message-ID: <bug-26903-4717-ho3UVzOTaL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26903-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26903
--- Comment #8 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> With current trunk I see these FAILS:
> ...
> FAIL: gdb.ada/array_of_variant.exp: scenario=minimal: print entire array
I looked into this one. With gcc-8 we have:
...
<1><1769>: Abbrev Number: 21 (DW_TAG_array_type)
<176a> DW_AT_name : (indirect string, offset: 0x20ad): p__array_t
<176e> DW_AT_type : <0x1758>
<1772> DW_AT_sibling : <0x1781>
<2><1776>: Abbrev Number: 22 (DW_TAG_subrange_type)
<1777> DW_AT_type : <0x1751>
<177b> DW_AT_upper_bound : 4 byte block: 91 b8 7f 6 (DW_OP_fbreg:
-72; DW_OP_deref)
<2><1780>: Abbrev Number: 0
...
but with gcc-7:
...
<1><9a5>: Abbrev Number: 22 (DW_TAG_array_type)
<9a6> DW_AT_name : (indirect string, offset: 0xd90): p__array_t
<9aa> DW_AT_type : <0x994>
<9ae> DW_AT_sibling : <0x9b8>
<2><9b2>: Abbrev Number: 23 (DW_TAG_subrange_type)
<9b3> DW_AT_type : <0x98d>
<2><9b7>: Abbrev Number: 0
...
So, the DW_AT_upper_bound is missing, IWO this looks like an xfail.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-07-26 10:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 14:09 [Bug ada/26903] New: " vries at gcc dot gnu.org
2020-11-16 14:13 ` [Bug ada/26903] " vries at gcc dot gnu.org
2020-11-16 14:13 ` vries at gcc dot gnu.org
2020-11-16 14:14 ` vries at gcc dot gnu.org
2020-11-16 14:17 ` vries at gcc dot gnu.org
2020-11-16 14:28 ` vries at gcc dot gnu.org
2020-11-16 14:29 ` vries at gcc dot gnu.org
2021-07-19 8:50 ` vries at gcc dot gnu.org
2021-07-19 9:10 ` vries at gcc dot gnu.org
2021-07-26 10:36 ` vries at gcc dot gnu.org [this message]
2021-07-26 20:11 ` vries at gcc dot gnu.org
2021-07-27 7:33 ` vries at gcc dot gnu.org
2021-07-27 8:17 ` [Bug testsuite/26903] " vries at gcc dot gnu.org
2021-07-27 14:56 ` cvs-commit at gcc dot gnu.org
2021-07-27 15:14 ` cvs-commit at gcc dot gnu.org
2021-07-27 15:15 ` vries 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-26903-4717-ho3UVzOTaL@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: 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).