From: Tom Tromey <tom@tromey.com>
To: Gary Benson via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] KFAIL variable-length array tests which fail with Clang
Date: Wed, 18 Nov 2020 09:14:44 -0700 [thread overview]
Message-ID: <87mtzek5fv.fsf@tromey.com> (raw)
In-Reply-To: <1605547055-25778-1-git-send-email-gbenson@redhat.com> (Gary Benson via Gdb-patches's message of "Mon, 16 Nov 2020 17:17:35 +0000")
>>>>> "Gary" == Gary Benson via Gdb-patches <gdb-patches@sourceware.org> writes:
Gary> Clang describes the upper bounds of variable length arrays using
Gary> a DW_AT_count attribute which references the DIE of a synthetic
Gary> variable whose value is specified using a DW_AT_location. In
Gary> some cases GDB correctly handles these, but in other cases GDB
Gary> adds an extra dereference causing the test to fail. This commit
Gary> marks these failing tests as caused by PR gdb/26905 when the
Gary> test executable was built using Clang.
Shouldn't we just fix the gdb bug instead?
Or is there something preventing that? I feel like I may not fully
appreciate the problem.
Tom
next prev parent reply other threads:[~2020-11-18 16:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 17:17 Gary Benson via Gdb-patches
2020-11-18 16:14 ` Tom Tromey [this message]
2020-11-19 22:53 ` Tom de Vries
2020-11-20 15:15 ` [PATCH][gdb/symtab] Fix gdb.base/vla-optimized-out.exp with clang Tom de Vries
2020-11-21 17:16 ` [gdb/testsuite] Add clang xfail in gdb.base/vla-ptr.exp Tom de Vries
2020-11-20 15:50 ` [PATCH] KFAIL variable-length array tests which fail with Clang Tom Tromey
2020-11-20 16:30 ` Tom de Vries
2020-11-20 16:51 ` Tom Tromey
2020-11-23 10:34 ` [PATCH][gdb/symtab] Fix gdb.base/vla-optimized-out.exp with clang Tom de Vries
2020-11-25 14:50 ` Gary Benson via Gdb-patches
2020-11-25 15:25 ` Gary Benson via Gdb-patches
2020-11-25 20:05 ` Tom de Vries
2020-11-26 10:10 ` Gary Benson via Gdb-patches
2020-11-30 12:51 ` [committed][PATCH][gdb/symtab] " Tom de Vries
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=87mtzek5fv.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@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