From: Eli Zaretskii <eliz@gnu.org>
To: Jacob Potter <jdpotter@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Use data cache for stack accesses
Date: Thu, 09 Jul 2009 12:20:00 -0000 [thread overview]
Message-ID: <83d48azhav.fsf@gnu.org> (raw)
In-Reply-To: <7e6c8d660907081308r13bff580rdcf4822c77df8403@mail.gmail.com>
> Date: Wed, 8 Jul 2009 13:08:00 -0700
> From: Jacob Potter <jdpotter@google.com>
>
> This is the second half of the pair of patches I first submitted last
> week. Differences from the first pass are:
>
> - Added a NEWS entry for the new option
> - Changed the stackcache option to default to on, rather than off
> - Got rid of the unnecessary new value_at_lazy_stack() function
> - Flush the cache when switching inferiors.
Thanks.
> I haven't changed the new read_stack function to take a target_ops,
> since it's intended to be consistent with read_memory(); converting
> read_memory() to take target_ops would be out of the scope of this
> patch (it and target_read_memory have a *lot* of callers). Other than
> that, I think I've addressed all the issues with the first pass; is
> there anything else to fix?
The NEWS entry is approved. But we need a patch for the manual that
describes the new command and removes the description of remotecache.
prev parent reply other threads:[~2009-07-09 3:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 20:49 Jacob Potter
2009-07-08 20:51 ` Pedro Alves
2009-07-08 20:58 ` Pedro Alves
2009-07-08 23:46 ` Daniel Jacobowitz
2009-07-09 3:06 ` Pedro Alves
2009-07-10 9:34 ` Pedro Alves
2009-07-10 8:45 ` Jacob Potter
2009-07-10 14:19 ` Pedro Alves
2009-07-13 19:25 ` Jacob Potter
2009-08-21 6:25 ` Doug Evans
2009-08-25 3:00 ` Doug Evans
2009-08-25 18:55 ` Pedro Alves
2009-08-26 16:36 ` Doug Evans
2009-08-26 22:45 ` Pedro Alves
2009-08-27 0:46 ` Doug Evans
2009-08-27 3:11 ` Doug Evans
2009-08-29 5:16 ` Doug Evans
2009-08-29 18:28 ` Doug Evans
2009-08-29 20:25 ` Pedro Alves
2009-09-02 20:43 ` Tom Tromey
2009-09-03 15:38 ` Doug Evans
2009-09-03 19:38 ` Tom Tromey
2009-09-03 19:45 ` Daniel Jacobowitz
2009-07-09 12:20 ` Eli Zaretskii [this message]
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=83d48azhav.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jdpotter@google.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