From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH v6] Fix range end handling of inlined subroutines
Date: Fri, 1 Jan 2021 14:41:01 -0500 [thread overview]
Message-ID: <e1244ba1-4586-3d82-a57e-7e2d55f2f47b@polymtl.ca> (raw)
In-Reply-To: <HE1PR0602MB3417B82A6028274A529E6168E4D50@HE1PR0602MB3417.eurprd06.prod.outlook.com>
On 2021-01-01 4:57 a.m., Bernd Edlinger wrote:
> Hi,
>
> this is the main part of the patch, which fixes the range end handling,
> and depends on the is_weak line table flag from the previous patch.
>
> I moved the entry_pc handling fix to a follow-up patch, as the
> test cases do not depend on it.
>
>
> Thanks
> Bernd.
>
This patch depends on the other one ("Introduce a new line table flag is_weak"),
right? Could you send it as a series? Normally, that's easily done using
git-send-email, although you don't seem to use git-send-email.
Simon
next prev parent reply other threads:[~2021-01-01 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-01 9:57 Bernd Edlinger
2021-01-01 19:41 ` Simon Marchi via Gdb-patches [this message]
2021-01-02 9:30 ` Bernd Edlinger
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=e1244ba1-4586-3d82-a57e-7e2d55f2f47b@polymtl.ca \
--to=gdb-patches@sourceware.org \
--cc=bernd.edlinger@hotmail.de \
--cc=simon.marchi@polymtl.ca \
/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