From: Simon Marchi <simark@simark.ca>
To: "Achra, Nitika" <Nitika.Achra@amd.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Ali Tamur <tamur@google.com>,
"George, Jini Susan" <JiniSusan.George@amd.com>
Subject: Re: [PATCH] Support for DWARF5 location lists entries
Date: Thu, 16 Jan 2020 14:16:00 -0000 [thread overview]
Message-ID: <726ebd81-48b2-684d-d4b5-8cdcf315d737@simark.ca> (raw)
In-Reply-To: <MN2PR12MB37440227F37410FF4F5F6D7E9A360@MN2PR12MB3744.namprd12.prod.outlook.com>
On 2020-01-16 6:29 a.m., Achra, Nitika wrote:
> [AMD Official Use Only - Internal Distribution Only]
>
> Hi Simon,
>
> Please find the attachment.
>
>
> *Handle DW_LLE_base_addressx, DW_LLE_startx_length and DW_LLE_start_length.
>
> Tested by running the testsuite before and after the patch and there is no increase in the number of test cases that fails.
> Tested with both -gdwarf-4 and -gdwarf-5 flags. Also tested -gslit-dwarf along with -gdwarf-4 as well as -gdwarf5 flags.
>
>
> gdb/ChangeLog:
> *dwarf2loc.c (decode_debug_loclists_addresses): Handle
> DW_LLE_base_addressx, DW_LLE_startx_length, DW_LLE_start_length.
>
> This is an effort to support DWARF5 in gdb.
Hi Achra,
The commit message of the patch is empty. The text that is above, which describes what
your patch does, should be placed in your git commit, such that it will appear in the
patch file when you use "git format-patch".
This is the text that people will see when they do "git log", so you can do "git log"
to see how it's usually formatted.
Thanks,
Simon
next prev parent reply other threads:[~2020-01-16 14:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-31 9:41 Achra, Nitika
2019-12-31 18:33 ` Simon Marchi
2020-01-06 7:22 ` Achra, Nitika
2020-01-06 10:14 ` Achra, Nitika
2020-01-08 3:26 ` Simon Marchi
2020-01-13 12:50 ` Achra, Nitika
2020-01-13 16:54 ` Simon Marchi
2020-01-14 8:04 ` Achra, Nitika
2020-01-14 16:56 ` Simon Marchi
2020-01-16 11:29 ` Achra, Nitika
2020-01-16 14:16 ` Simon Marchi [this message]
2020-01-16 14:29 ` Simon Marchi
2020-01-16 15:48 ` Achra, Nitika
2020-01-16 17:28 ` Simon Marchi
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=726ebd81-48b2-684d-d4b5-8cdcf315d737@simark.ca \
--to=simark@simark.ca \
--cc=JiniSusan.George@amd.com \
--cc=Nitika.Achra@amd.com \
--cc=gdb-patches@sourceware.org \
--cc=tamur@google.com \
/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