From: Tom Tromey <tom@tromey.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Keith Seitz <keiths@redhat.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [RFC/PATCH] Fix dwarf2read.c:dwarf2_find_containing_comp_unit's binary search
Date: Sun, 16 Dec 2018 16:44:00 -0000 [thread overview]
Message-ID: <87pnu14e1e.fsf@tromey.com> (raw)
In-Reply-To: <87a7llnsn1.fsf@redhat.com> (Sergio Durigan Junior's message of "Tue, 04 Dec 2018 11:50:10 -0500")
>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:
>> Is this needed for 8.2 branch?
Sergio> Yep, I'd say so. This seems like a simple patch to be backported to
Sergio> 8.2, but I'll wait for a global maintainer to give the green light so
Sergio> that I can create a proper bug.
Did anyone ever reply to this?
It seems like a good fix to backport to me.
Tom
next prev parent reply other threads:[~2018-12-16 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 17:22 Sergio Durigan Junior
2018-11-30 17:52 ` Tom Tromey
2018-11-30 18:05 ` Sergio Durigan Junior
2018-12-04 16:44 ` Keith Seitz
2018-12-04 16:50 ` Sergio Durigan Junior
2018-12-16 16:44 ` Tom Tromey [this message]
2018-12-18 15:48 ` Sergio Durigan Junior
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=87pnu14e1e.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
--cc=sergiodj@redhat.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