From: "H.J. Lu" <hjl.tools@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
GDB <gdb-patches@sourceware.org>
Subject: Re: [commit 7.8] [patch+7.8] Fix 7.8 regression: resolve_dynamic_struct: Assertion `TYPE_NFIELDS (type) > 0' (PR 17642)
Date: Mon, 15 Dec 2014 22:11:00 -0000 [thread overview]
Message-ID: <CAMe9rOpkZbwKT62xeAKuStqqAXspRZM=+m=E0Fi=LFGgGS=_Mg@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOoxqGcQ+u8OdqxW2xW3OqxCo1dt4c2ULy+sfS--qRc=fQ@mail.gmail.com>
On Mon, Dec 15, 2014 at 1:09 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Mon, Dec 15, 2014 at 12:41 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>>> > This is a fairly big patch...
>>> > 1. How bad is performance without it?
>>>
>>> It was very bad, like > 100x slower.
>>
>> OK, but 100x slower than 1usec is still unnoticeable. When did you start
>> noticing it, for what kind of program (size?), and what type of delay
>> were you seeing? Also, is that a regression compared to 7.7? The idea
>> is that, if it's just a second or two, or even ten, that's still quite
>> bearable, and unless you are absolutely sure that your patch is safe,
>> perhaps we should pass...
>>
>>> > 2. Can you find a binutils maintainer that will vouch that
>>> > this patch is 100% safe?
>>>
>>> As the x86 binutils maintainer, do I count?
>>
>> Absolutely. I just need someone who knows the code well enough to
>> be trusted with its maintainance to stand behind the code and
>> confirm that it is considered safe. In this case, I need extra safe,
>> considering the fact that this is a .2 release.
>>
>> I hope I've described my concerns well enough for you to make
>> the decision. Now that I have explained my thought process, I feel
>> you're more qualified to make an informed decision now. Your call.
>>
>> Please remember that, if you do push it to 7.8, you'll need a PR
>> associated to is so you can document the fix in the release wiki
>> page (see fixes in GDB 7.8.2):
>> https://sourceware.org/gdb/wiki/GDB_7.8_Release
>
> The bug was filed against bintuils:
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=17677
>
> since the code in question is in bfd. But the actual bug is for GDB:
>
> https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1388999
>
> where the issues was observed. I will retest by my patch and
> backport it to 7.8 branch.
>
There is no regression in GDB 7.8 testsuite. I pushed my change
into 7.8 branch. Its PR is
https://sourceware.org/bugzilla/show_bug.cgi?id=17677
Thanks.
--
H.J.
next prev parent reply other threads:[~2014-12-15 22:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 19:54 Jan Kratochvil
2014-12-13 14:23 ` Joel Brobecker
2014-12-13 14:39 ` [commit] " Jan Kratochvil
2014-12-13 18:18 ` Doug Evans
2014-12-15 15:06 ` Joel Brobecker
2014-12-15 15:21 ` Jan Kratochvil
2014-12-15 19:12 ` [commit 7.8] " Jan Kratochvil
2014-12-15 19:23 ` H.J. Lu
2014-12-15 19:37 ` Joel Brobecker
2014-12-15 20:02 ` H.J. Lu
2014-12-15 20:41 ` Joel Brobecker
2014-12-15 21:09 ` H.J. Lu
2014-12-15 22:11 ` H.J. Lu [this message]
2014-12-15 22:44 ` Joel Brobecker
2014-12-15 22:53 ` H.J. Lu
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='CAMe9rOpkZbwKT62xeAKuStqqAXspRZM=+m=E0Fi=LFGgGS=_Mg@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).