From: Yao Qi <qiyaoltc@gmail.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Make file-based lookup more interruptable
Date: Tue, 02 Jun 2015 07:59:00 -0000 [thread overview]
Message-ID: <556D6267.5080408@gmail.com> (raw)
In-Reply-To: <CADPb22TDaetTJyuTHPJboyziJAzoP88N7Gii6iOYfTmPXsNCLg@mail.gmail.com>
[Sorry for being late]
On 22/05/15 18:46, Doug Evans wrote:
> I'd classify this as being no different than a performance improvement.
I think they are different. IMO, performance improvement is the time
or memory reduction to some degree. This kind of change can be user
visible (10 min -> 10s) and can be user invisible (2s -> 1s).
> There already is a level of interruptability, the only change is in degree
> of responsiveness.
>
> We*can* start adding such things to NEWS, but we don't do so today.
> Before we start imposing this on everyone, we'll need to establish
> what does and does not qualify - I'm guessing we don't want to add
> a NEWS entry for every little performance improvement.
However, this change isn't performance improvement, because it doesn't
shorten the time of operation like "b 'foo.c':bar". This change only
makes GDB more interruptable during some operations, IMO this is a good
news to users and we should let them know.
Regarding to NEWS entry for performance improvement, I don't have an
opinion on it.
--
Yao (é½å°§)
next prev parent reply other threads:[~2015-06-02 7:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 22:20 Doug Evans
2015-05-19 11:55 ` Yao Qi
2015-05-22 17:46 ` Doug Evans
2015-06-02 0:03 ` Doug Evans
2015-06-02 7:59 ` Yao Qi [this message]
2015-06-02 12:34 ` Doug Evans
2015-06-02 13:08 ` Yao Qi
2015-06-02 13:20 ` Doug Evans
2015-06-02 13:46 ` Yao Qi
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=556D6267.5080408@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=dje@google.com \
--cc=gdb-patches@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