Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <xdje42@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] symbol lookup cache
Date: Sat, 20 Dec 2014 19:55:00 -0000	[thread overview]
Message-ID: <83k31mqeoa.fsf@gnu.org> (raw)
In-Reply-To: <CAP9bCMTemYD6-X55OMacphFY6PcAan8Vr9E_Rh43KN=x4_NB7Q@mail.gmail.com>

> Date: Sat, 20 Dec 2014 11:14:39 -0800
> From: Doug Evans <xdje42@gmail.com>
> Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
> 
> > Btw, I wonder if this should be a user option, not a "maint" option.
> > The heuristics used to determine the cache size tend to be wrong in
> > some rare corner cases, so letting the user override this should be a
> > good thing, I think.
> 
> The thought is the fewer knobs the user needs the better,

We are way past the point where this ideal was achievable.  You can
stop worrying about that.  With the gazillion knobs we have already,
one more doesn't change anything.


  reply	other threads:[~2014-12-20 19:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-01  8:23 [RFC] " Doug Evans
2014-12-03  0:50 ` Doug Evans
2014-12-20  7:57   ` [PATCH] " Doug Evans
2014-12-20  8:29     ` Doug Evans
2014-12-20 10:43     ` Eli Zaretskii
2014-12-20 19:14       ` Doug Evans
2014-12-20 19:55         ` Eli Zaretskii [this message]
2014-12-20 21:04           ` Doug Evans
2014-12-21  3:34             ` Eli Zaretskii
2014-12-21 18:51               ` Doug Evans
2014-12-21 21:01                 ` Joel Brobecker
2014-12-22  2:04                   ` Doug Evans
2014-12-22 12:48                     ` Joel Brobecker
2015-01-11 19:11                       ` Doug Evans
2014-12-03  2:46 ` [RFC] " Joel Brobecker
2014-12-04 16:38 ` Pedro Alves
2014-12-04 19:17   ` Doug Evans
2014-12-04 19:16 ` Jan Kratochvil
2014-12-04 19:24   ` Doug Evans
2014-12-04 19:28     ` Jan Kratochvil

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=83k31mqeoa.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=xdje42@gmail.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