Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Gary Benson <gbenson@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [committed][gdb/testsuite] Update psym-external-decl.exp for gcc-10/clang
Date: Fri, 19 Jun 2020 16:06:37 +0200	[thread overview]
Message-ID: <6dd30362-e9dd-6bc9-bf40-8b846b926e5a@suse.de> (raw)
In-Reply-To: <20200619140041.GB31823@blade.nx>

On 6/19/20 4:00 PM, Gary Benson wrote:
> Tom de Vries wrote:
>> On 6/18/20 6:10 PM, Gary Benson wrote:
>>> Tom de Vries wrote:
>>>> On 6/17/20 2:24 PM, Gary Benson wrote:
>>>>> Tom de Vries wrote:
>>>>>> diff --git a/gdb/testsuite/gdb.base/psym-external-decl.exp b/gdb/testsuite/gdb.base/psym-external-decl.exp
>>>>>> index bbcc2745755..d0388d5655e 100644
>>>>>> --- a/gdb/testsuite/gdb.base/psym-external-decl.exp
>>>>>> +++ b/gdb/testsuite/gdb.base/psym-external-decl.exp
> [nsip]
>>>>> Tom, I'd like this testcase to not fail silently.  Is the
>>>>> functionality under test something that isn't ever expected to
>>>>> work with clang, or is this a test that should pass with clang
>>>>> (but it currently doesn't, for whatever reason)?
>>>>
>>>> I'm not sure.  The test can pass with clang, provided it generates the
>>>> required debug info.  It currently doesn't.  Why that is the case, I
>>>> have no idea.
>>>
>>> I think that means the test should work but it doesn't.  Would you
>>> object if I push a patch removing the test-skipping logic?  It will
>>> mean an extra FAIL when tested using clang
>>
>> I don't think having a fail for a compiler bug/missing-feature is a
>> good idea.
>>
>> If this is due to a bug/missing-feature in clang, then we need to:
>> - xfail the test,
>> - file the PR in clang, and
>> - reference the PR at the xfail.
> 
> Is this a bug/missing feature in clang though?
> How sure are you GDB isn't at fault?

Clang emits less debug info than GCC.  Whether that's a bug, a missing
feature or an explicit unsupported feature in clang, I don't known.

I known that gdb isn't at fault.  It can't do anything without the
missing debug info.  The test was specifically written to use that debug
info.

Thanks,
- Tom


  reply	other threads:[~2020-06-19 14:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-02  7:51 Tom de Vries
2020-06-17 12:24 ` Gary Benson
2020-06-17 13:56   ` Tom de Vries
2020-06-18 16:10     ` Gary Benson
2020-06-18 16:27       ` Tom de Vries
2020-06-19 14:00         ` Gary Benson
2020-06-19 14:06           ` Tom de Vries [this message]
2020-06-26  9:37             ` Gary Benson
2020-06-28 10:50               ` Tom de Vries
2020-06-29 12:32                 ` Pedro Alves
2020-06-30  8:14                   ` Tom de Vries
2020-07-03  9:21                     ` Gary Benson
2020-07-03 11:20                       ` Pedro Alves
2020-07-03 11:24                         ` Tom de Vries
2020-07-03 11:32                           ` Pedro Alves
2020-07-03 12:50                             ` 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=6dd30362-e9dd-6bc9-bf40-8b846b926e5a@suse.de \
    --to=tdevries@suse.de \
    --cc=gbenson@redhat.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