From: "George, Jini Susan" <JiniSusan.George@amd.com>
To: 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, 7 Jun 2022 06:42:44 +0000 [thread overview]
Message-ID: <BY5PR12MB496580FFB60C5C79B2D6289290A59@BY5PR12MB4965.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220526151041.23223-4-blarsen@redhat.com>
[Public]
Hi Bruno,
Now that with Kavitha's changes, we have clang emitting debug information for alias variables (https://reviews.llvm.org/D120989) and since we have her gdb patch (awaiting final approval) to enable support for clang emitted alias debug information, (https://sourceware.org/pipermail/gdb-patches/2022-April/188354.html), maybe we can wait on this ? If her patch goes through, we wouldn't have to make this test case an xfail.
Let me know if you think otherwise.
Thanks,
Jini.
>>-----Original Message-----
>>From: Gdb-patches <gdb-patches-
>>bounces+jigeorge=amd.com@sourceware.org> On Behalf Of Bruno Larsen via
>>Gdb-patches
>>Sent: Thursday, May 26, 2022 8:41 PM
>>To: gdb-patches@sourceware.org
>>Subject: [PATCH v3 03/14] change gdb.base/symbol-alias to xfail with clang
>>
>>[CAUTION: External Email]
>>
>>Clang does not issue alias information, even when using -gfull. This commit
>>adds an xfail to that test in case we are using clang to reduce noise when
>>testing.
>>---
>>
>>No change in v3
>>
>>no change in v2
>>
>>---
>> 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..f2b675e09ff 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 doesn't include variable alias information in the dwarf:
>>+#
>>+https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithu
>>+b.com%2Fllvm%2Fllvm-
>>project%2Fissues%2F52664&data=05%7C01%7CJiniSus
>>+an.George%40amd.com%7C8b9c790bd30245184ac808da3f2a368f%7C3dd896
>>1fe4884e
>>+608e11a82d994e183d%7C0%7C0%7C637891747783140459%7CUnknown%7C
>>TWFpbGZsb3d
>>+8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3
>>D%7C3
>>+000%7C%7C%7C&sdata=8P8eeL5Y%2FlthVzjmehnJ8i1PTBMI1zy8t8TgEHF
>>%2FnHc%
>>+3D&reserved=0
>>+if [test_compiler_info {clang*}] {
>>+ setup_xfail "clang/52664" *-*-*
>> }
>>+gdb_test "p g_var_s_alias" "= {field1 = 1, field2 = 2}"
>>--
>>2.31.1
next prev parent reply other threads:[~2022-06-07 6:42 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 [this message]
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
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=BY5PR12MB496580FFB60C5C79B2D6289290A59@BY5PR12MB4965.namprd12.prod.outlook.com \
--to=jinisusan.george@amd.com \
--cc=Kavitha.Natarajan@amd.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).