public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Pedro Alves <pedro@palves.net>, 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, 3 Jul 2020 13:24:34 +0200	[thread overview]
Message-ID: <5197d5fc-1a9d-b61d-71a5-864b2133f13b@suse.de> (raw)
In-Reply-To: <a11f10e0-9700-c35b-56d3-813c92be180a@palves.net>

On 7/3/20 1:20 PM, Pedro Alves wrote:
> On 7/3/20 10:21 AM, Gary Benson wrote:
>> Tom de Vries wrote:
>>> On 6/29/20 2:32 PM, Pedro Alves wrote:
> 
>>>> I would suggest filing a bug with clang, to confirm whether
>>>> this is intentional, or whether they see it as a bug.  I would
>>>> think it is a bug, but I'm not sure.  If indeed a bug, we would
>>>> XFAIL the test.
>>>
>>> I've filed https://bugs.llvm.org/show_bug.cgi?id=46514 .
>>>
>>> Thanks,
>>> - Tom
>>
>> Thank for filing it Tom.
> 
> So the conclusion seems to be that the testcase should be using
> -fstandalone-debug?
> 
> Except, I tried it here, and it doesn't seem to work:
> 

It is my understanding that -fstandalone-debug should be used for clang,
but that is doesn't work atm, which is a problem in clang/llvm that is
tracked in the PR.

Thanks,
- Tom

> ~~~~~~~~~~~~~~~~
> From 792aa03ab3325fe7cfcfeb51e765e81da2fbbfaf Mon Sep 17 00:00:00 2001
> From: Pedro Alves <palves@redhat.com>
> Date: Fri, 3 Jul 2020 12:12:19 +0100
> Subject: [PATCH] standalone
> 
> ---
>  gdb/testsuite/gdb.base/psym-external-decl.exp | 9 +++++----
>  1 file changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/gdb/testsuite/gdb.base/psym-external-decl.exp b/gdb/testsuite/gdb.base/psym-external-decl.exp
> index d0388d5655e..faff3234bb5 100644
> --- a/gdb/testsuite/gdb.base/psym-external-decl.exp
> +++ b/gdb/testsuite/gdb.base/psym-external-decl.exp
> @@ -15,17 +15,18 @@
>  
>  standard_testfile .c psym-external-decl-2.c
>  
> +set srcfiles [list $srcfile $srcfile2]
> +set options {debug}
> +
>  get_compiler_info
>  if { [test_compiler_info "clang-*"] } {
> -    return -1
> +    lappend options additional_flags=-fstandalone-debug
>  }
>  
> -set srcfiles [list $srcfile $srcfile2]
> -
>  if { [build_executable_from_specs \
>  	  "failed to prepare" \
>  	  $testfile [list] \
> -	  $srcfile [list debug] \
> +	  $srcfile $options \
>  	  $srcfile2 [list]] == -1 } {
>      return -1
>  }
> 
> base-commit: c2ecccb33c307faa21f4d2f47348e7346b032d94
> 

  reply	other threads:[~2020-07-03 11:24 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
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 [this message]
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=5197d5fc-1a9d-b61d-71a5-864b2133f13b@suse.de \
    --to=tdevries@suse.de \
    --cc=gbenson@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    /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).