From: Keith Seitz <keiths@redhat.com>
To: "Tomar, Sourabh Singh" <SourabhSingh.Tomar@amd.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Macro info NOT accessible with GDB-trunk
Date: Mon, 17 May 2021 10:22:18 -0700 [thread overview]
Message-ID: <d52a8679-fe4d-5c8a-f35c-dff79e89f586@redhat.com> (raw)
In-Reply-To: <DM4PR12MB52954D49AD3DFB942D8561EB9D2D9@DM4PR12MB5295.namprd12.prod.outlook.com>
On 5/17/21 10:04 AM, Tomar, Sourabh Singh wrote:
> [AMD Public Use]
>
> Thanks For the quick response keith!
>
> Do you have any pointers to the base commit/change that might've caused this ?
Sorry, I do not, but gdb/27306 was originally filed in February against 10.1.
So if it's a recent change, "recent" would necessarily mean at least 9+ months
ago when 10.1 was branched.
My feeling is that this is more a result of a gcc change than something in
gdb, but don't quote me on that. :-)
Keith
next prev parent reply other threads:[~2021-05-17 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 16:35 Tomar, Sourabh Singh
2021-05-17 16:51 ` Keith Seitz
2021-05-17 17:04 ` Tomar, Sourabh Singh
2021-05-17 17:17 ` Tomar, Sourabh Singh
2021-05-17 17:22 ` Keith Seitz [this message]
2021-09-16 4:18 ` Achra, Nitika
2021-10-04 3:46 ` Achra, Nitika
2021-10-06 16:11 ` Keith Seitz
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=d52a8679-fe4d-5c8a-f35c-dff79e89f586@redhat.com \
--to=keiths@redhat.com \
--cc=SourabhSingh.Tomar@amd.com \
--cc=gdb@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).