public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Natarajan, Kavitha" <Kavitha.Natarajan@amd.com>
To: Bruno Larsen <blarsen@redhat.com>,
	"Natarajan, Kavitha via Gdb-patches" <gdb-patches@sourceware.org>
Cc: "George, Jini Susan" <JiniSusan.George@amd.com>,
	"Parasuraman, Hariharan" <Hariharan.Parasuraman@amd.com>
Subject: RE: [PATCH] Debug support for global alias variable
Date: Wed, 30 Mar 2022 11:30:56 +0000	[thread overview]
Message-ID: <DM4PR12MB5796473A359DA482DE64D6C5F71F9@DM4PR12MB5796.namprd12.prod.outlook.com> (raw)
In-Reply-To: <66ca57f9-c3b8-4aeb-f07c-c3c254dfdea6@redhat.com>

[AMD Official Use Only]

Hello Bruno,

Thanks again for the quick review. I have fixed all your comments. I understand
that you are working on cleanup of gdb.base for clang testing. Now all older clang
versions would XFAIL while the existing FAILs would PASS for clang with this fix.

> > -  /* If the die does not have a name, this is not a namespace
> > -     alias.  */
> > +  /* The die must have a name for namespace or variable alias.  */
> >     attr = dwarf2_attr (die, DW_AT_name, cu);
>
> Oops, I didn't catch this on my last review. DWARF 5 manual, section 3.2.3
> Imported (or Renamed) Declaration Entries, says:
>
> An imported declaration may also have a DW_AT_name attribute whose
> value is (...) If no name is present, then the name by which the entity is to be
> known is the same as the name of the entity being imported.
>
> So I think the check and the comment are incorrect (or the spec needs
> updating). I know this isn't something you added, but since you are changing
> this function, I think it could be a good time to update this.

I have modified the comment. If no name is present, there is no need to create
a new symbol for the namespace or variable alias. So nothing to do in this function
and it returns false. The name of the imported entity is used in this case
("using" statements in your example).

Regards,
Kavitha

  reply	other threads:[~2022-03-30 11:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-04 13:44 Natarajan, Kavitha
2022-03-14 11:15 ` Natarajan, Kavitha
2022-03-24  6:36   ` Natarajan, Kavitha
2022-03-24 13:53 ` Bruno Larsen
2022-03-28 15:14   ` Natarajan, Kavitha
2022-03-29 14:02     ` Bruno Larsen
2022-03-30 11:30       ` Natarajan, Kavitha [this message]
2022-03-30 12:25         ` Natarajan, Kavitha
2022-04-05  6:26           ` Natarajan, Kavitha
2022-04-05 13:33           ` Bruno Larsen
2022-04-05 14:02             ` Natarajan, Kavitha
2022-04-12  8:38             ` Natarajan, Kavitha
2022-04-15 16:06           ` Tom Tromey
2022-04-18 11:04             ` Natarajan, Kavitha
2022-04-18 15:03               ` Tom Tromey
2022-04-19 12:45                 ` Natarajan, Kavitha
2022-04-19 22:59                   ` Tom Tromey
2022-04-20  6:00                     ` Natarajan, Kavitha
2022-04-20 10:33                       ` Pedro Alves
2022-04-20 12:17                         ` Natarajan, Kavitha
2022-04-25 13:10                           ` Natarajan, Kavitha
2022-05-05  9:53                           ` Natarajan, Kavitha
2022-06-07  9:08                           ` Natarajan, Kavitha
2022-06-08 16:29                             ` Pedro Alves
2022-06-09 11:36                               ` Pedro Alves
2022-06-13 11:11                                 ` Natarajan, Kavitha
2022-06-13 13:54                                   ` Pedro Alves
2022-06-13 17:28                                     ` Natarajan, Kavitha

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=DM4PR12MB5796473A359DA482DE64D6C5F71F9@DM4PR12MB5796.namprd12.prod.outlook.com \
    --to=kavitha.natarajan@amd.com \
    --cc=Hariharan.Parasuraman@amd.com \
    --cc=JiniSusan.George@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).