public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "George, Jini Susan" <JiniSusan.George@amd.com>
To: Andrew Burgess <aburgess@redhat.com>,
	Bruno Larsen <blarsen@redhat.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "Natarajan, Kavitha" <Kavitha.Natarajan@amd.com>
Subject: RE: [PATCH v3 03/14] change gdb.base/symbol-alias to xfail with clang
Date: Tue, 14 Jun 2022 07:23:42 +0000	[thread overview]
Message-ID: <BY5PR12MB496507B608C70CC0ED55B02290AA9@BY5PR12MB4965.namprd12.prod.outlook.com> (raw)
In-Reply-To: <BY5PR12MB496554D42DFA1866BC7906CA90AA9@BY5PR12MB4965.namprd12.prod.outlook.com>

[Public]

I missed mentioning that Kavitha's patch takes care of making symbol-alias.exp xfail for clang versions less than 15.

Thanks,
Jini.

>>-----Original Message-----
>>From: Gdb-patches <gdb-patches-
>>bounces+jigeorge=amd.com@sourceware.org> On Behalf Of George, Jini Susan
>>via Gdb-patches
>>Sent: Tuesday, June 14, 2022 12:44 PM
>>To: Andrew Burgess <aburgess@redhat.com>; Bruno Larsen
>><blarsen@redhat.com>; gdb-patches@sourceware.org
>>Cc: Natarajan, Kavitha <Kavitha.Natarajan@amd.com>
>>Subject: RE: [PATCH v3 03/14] change gdb.base/symbol-alias to xfail with clang
>>
>>[Public]
>>
>>[CAUTION: External Email]
>>
>>[Public]
>>
>>Now that Kavitha's patch just got committed (details below), guess we might not
>>require this.
>>
>>commit 6df97c56ea0f3086c96743ec47148ee69fd8cf71 (HEAD -> master,
>>origin/master, origin/HEAD)
>>Author: Kavitha Natarajan <kavitha.natarajan@amd.com>
>>Date:   Tue Jun 14 10:37:46 2022 +0530
>>
>>    Debug support for global alias variable
>>
>>    Starting with (future) Clang 15 (since
>>
>>https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Freviews.
>>llvm.org%2FD120989&amp;data=05%7C01%7CJiniSusan.George%40amd.com%
>>7Ce7ea873468214efcf9d908da4dd648a2%7C3dd8961fe4884e608e11a82d994e
>>183d%7C0%7C0%7C637907879987330246%7CUnknown%7CTWFpbGZsb3d8eyJ
>>WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C
>>3000%7C%7C%7C&amp;sdata=bNOSusnr0cUBWttQ1PM8JrnijdjPJl2ee7lBpPsStY
>>A%3D&amp;reserved=0), Clang emits the DWARF information
>>    of global alias variables as DW_TAG_imported_declaration.  However,
>>    GDB does not handle it.  It incorrectly always reads this tag as
>>    C++/Fortran imported declaration (type alias, namespace alias and
>>    Fortran module).  This commit adds support to handle this tag as an
>>    alias variable.
>>
>>    This change fixes the failures in the gdb.base/symbol-alias.exp
>>    testcase with current git Clang.  This testcase is also updated to
>>    test nested (recursive) aliases.
>>
>>Thanks,
>>Jini.
>>
>>>>-----Original Message-----
>>>>From: Gdb-patches <gdb-patches-
>>>>bounces+jigeorge=amd.com@sourceware.org> On Behalf Of Andrew Burgess
>>>>via Gdb-patches
>>>>Sent: Friday, June 10, 2022 4:31 PM
>>>>To: Bruno Larsen <blarsen@redhat.com>; gdb-patches@sourceware.org
>>>>Subject: RE: [PATCH v3 03/14] change gdb.base/symbol-alias to xfail
>>>>with clang
>>>>
>>>>[CAUTION: External Email]
>>>>
>>>>Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org> writes:
>>>>
>>>>> Hi Jini,
>>>>>
>>>>> Great to hear that Kavitha's changes have landed on clang! I do
>>>>> think that it is still important to have xfails, however, since only
>>>>> new clangs would add the information, and GDB is tested in all
>>>>> manner of systems.
>>>>>
>>>>> I have changed the patch to assume that clang 15 has Kavitha's
>>>>> patches, and changed the clang compiler test.  Does this look acceptable?
>>>>>
>>>>> [PATCH v4 03/14] gdb/testsuite: Change gdb.base/symbol-alias to
>>>>> xfail with old clang
>>>>>
>>>>> Clang didn't use to add alias information, even when using -gfull.
>>>>> This commit checks if the clang version being used is already
>>>>> providing alias information (15 or newer), otherwise it adds an XFAIL.
>>>>
>>>>My understanding from Jini's email was that for this test to pass we
>>>>would also need this gdb patch:
>>>>
>>>>
>>>>https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsour
>>>>ce
>>>>ware.org%2Fpipermail%2Fgdb-patches%2F2022-
>>>>April%2F188354.html&amp;data=05%7C01%7CJiniSusan.George%40amd.com
>>%
>>>>7Ca2aaecea2df0476d781808da4ad0988b%7C3dd8961fe4884e608e11a82d99
>>4e
>>>>183d%7C0%7C0%7C637904557029019597%7CUnknown%7CTWFpbGZsb3d8e
>>yJ
>>>>WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%
>>7C
>>>>3000%7C%7C%7C&amp;sdata=8%2FUKHMbpyAKXN4HOPHRJ2vP62yKK5i5Qe
>>au
>>>>v0GQtWHo%3D&amp;reserved=0
>>>>
>>>>So, if I had clang 15 right now, this test would still fail, right?
>>>>
>>>>I guess you either need to hold this patch back until the above is
>>>>merged, or put this in with a generic "all clang" pattern (like you
>>>>originally had) and then assume someone will spot the KPASS and fix up the
>>test later.
>>>>
>>>>Also...
>>>>
>>>>
>>>>> ---
>>>>>  gdb/testsuite/gdb.base/symbol-alias.exp | 9 +++++++--
>>>>>  1 file changed, 7 insertions(+), 2 deletions(-)
>>>>>
>>>>> diff --git a/gdb/testsuite/gdb.base/symbol-alias.exp
>>>>> b/gdb/testsuite/gdb.base/symbol-alias.exp
>>>>> index 289f49bbc3f..078158dc101 100644
>>>>> --- a/gdb/testsuite/gdb.base/symbol-alias.exp
>>>>> +++ b/gdb/testsuite/gdb.base/symbol-alias.exp
>>>>> @@ -31,6 +31,11 @@ foreach f {"func" "func_alias"} {  }
>>>>>
>>>>>  # Variables.
>>>>> -foreach v {"g_var_s" "g_var_s_alias"} {
>>>>> -    gdb_test "p $v" "= {field1 = 1, field2 = 2}"
>>>>> +gdb_test "p g_var_s" "= {field1 = 1, field2 = 2}"
>>>>> +
>>>>> +# Clang didn't include alias information until version 15.
>>>>> +if {[test_compiler_info {clang-[1-9]*}]
>>>>> +     || [test_compiler_info {clang-1[0-4]*}]} {
>>>>
>>>>Wouldn't clang-15 match the first of these patterns?
>>>>
>>>>Thannks,
>>>>Andrew
>>>>
>>>>
>>>>> +    setup_xfail "clang/52664" *-*-*
>>>>>  }
>>>>> +gdb_test "p g_var_s_alias" "= {field1 = 1, field2 = 2}"
>>>>> --
>>>>> 2.31.1


  reply	other threads:[~2022-06-14  7:23 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26 15:10 [PATCH v3 00/14] Clean gdb.base when testing " Bruno Larsen
2022-05-26 15:10 ` [PATCH v3 01/14] gdb/testsuite: introduce gdb_step_until_regexp Bruno Larsen
2022-05-27 16:19   ` Andrew Burgess
2022-05-30 12:44     ` Bruno Larsen
2022-05-30 14:06       ` Andrew Burgess
2022-06-08 14:59     ` Pedro Alves
2022-05-26 15:10 ` [PATCH v3 02/14] Change gdb.base/skip-solib.exp deal with lack of epilogue information Bruno Larsen
2022-05-30 14:04   ` Andrew Burgess
2022-05-30 20:31     ` Bruno Larsen
2022-06-01 14:52     ` [PATCH] gdb/testsuite: Add test to step through function epilogue Bruno Larsen
2022-06-08 15:37   ` [PATCH v3 02/14] Change gdb.base/skip-solib.exp deal with lack of epilogue information Pedro Alves
2022-06-09 16:27     ` Bruno Larsen
2022-06-09 18:25       ` Pedro Alves
2022-06-09 18:55         ` Bruno Larsen
2022-06-13 15:32           ` Pedro Alves
2022-05-26 15:10 ` [PATCH v3 03/14] change gdb.base/symbol-alias to xfail with clang Bruno Larsen
2022-06-07  6:42   ` George, Jini Susan
2022-06-07 12:53     ` Bruno Larsen
2022-06-08  7:41       ` George, Jini Susan
2022-06-10 11:01       ` Andrew Burgess
2022-06-10 12:07         ` Bruno Larsen
2022-06-14  7:14         ` George, Jini Susan
2022-06-14  7:23           ` George, Jini Susan [this message]
2022-06-14 11:23             ` Bruno Larsen
2022-05-26 15:10 ` [PATCH v3 04/14] change gdb.base/nodebug.c to not fail " Bruno Larsen
2022-06-10 18:24   ` Andrew Burgess
2022-05-26 15:10 ` [PATCH v3 05/14] update gdb.base/info-program.exp " Bruno Larsen
2022-06-30 14:45   ` Andrew Burgess
2022-05-26 15:10 ` [PATCH v3 06/14] fix gdb.base/access-mem-running.exp for clang testing Bruno Larsen
2022-06-30 15:06   ` Andrew Burgess
2022-05-26 15:10 ` [PATCH v3 07/14] Fix gdb.base/call-ar-st to work with Clang Bruno Larsen
2022-05-26 15:10 ` [PATCH v3 08/14] add xfails to gdb.base/complex-parts.exp when testing with clang Bruno Larsen
2022-05-26 15:10 ` [PATCH v3 09/14] gdb/testsuite: fix gdb.base/msym-bp-shl when running with Clang Bruno Larsen
2022-05-26 15:10 ` [PATCH v3 10/14] explicitly test for stderr in gdb.base/dprintf.exp Bruno Larsen
2022-05-26 15:10 ` [PATCH v3 11/14] gdb/testsuite: Update gdb.base/so-impl-ld.exp Bruno Larsen
2022-05-26 15:10 ` [PATCH v3 12/14] [gdb/testsuite]: fix gdb.base/jit-elf.exp when testing with clang Bruno Larsen
2022-05-26 15:10 ` [PATCH v3 13/14] gdb/testsuite: fix gdb.base/info-types-c++ " Bruno Larsen
2022-05-26 15:10 ` [PATCH v3 14/14] gdb.base/skip.exp: Use finish to exit functions Bruno Larsen

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=BY5PR12MB496507B608C70CC0ED55B02290AA9@BY5PR12MB4965.namprd12.prod.outlook.com \
    --to=jinisusan.george@amd.com \
    --cc=Kavitha.Natarajan@amd.com \
    --cc=aburgess@redhat.com \
    --cc=blarsen@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).