Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Pedro Alves <palves@redhat.com>
Cc: Doug Evans <dje@google.com>,
	"Abid, Hafiz" <Hafiz_Abid@mentor.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	"Mirza, Taimoor"	<Taimoor_Mirza@mentor.com>
Subject: Re: [patch] Disassembly improvements
Date: Sat, 19 Oct 2013 01:55:00 -0000	[thread overview]
Message-ID: <5261E638.7030702@codesourcery.com> (raw)
In-Reply-To: <52617D1A.6010600@redhat.com>

On 10/19/2013 02:25 AM, Pedro Alves wrote:
> BTW, how will your "Read memory in multiple lines in dcache_xfer_memory"
> series help disassembly if the disassembler, today, without that other
> patch that caches things in disasm.c, fetches memory from the target
> instruction by instruction?  Seems to me it'll end up always fetching
> a single line at a time.

That series is to optimize dcache, since disassembly doesn't use dcache, 
that series doesn't help disassembly now.
Once we use dcache in disassembly (that is what I am doing), that series 
helps when users disassembly large functions.

-- 
Yao (齐尧)


  reply	other threads:[~2013-10-19  1:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-10 13:14 Abid, Hafiz
2013-10-10 13:34 ` Pedro Alves
2013-10-10 13:57   ` Abid, Hafiz
2013-10-10 14:52     ` Pedro Alves
2013-10-10 15:13       ` Pedro Alves
2013-10-11 16:45         ` Abid, Hafiz
2013-10-11 21:12           ` Pedro Alves
2013-10-11 21:34 ` Doug Evans
2013-10-14  9:37   ` Abid, Hafiz
2013-10-14 14:42   ` Pedro Alves
2013-10-16  1:16     ` Doug Evans
2013-10-16  7:53       ` Yao Qi
2013-10-16 12:08         ` Pedro Alves
2013-10-16 13:23           ` Yao Qi
2013-10-18 10:24           ` Yao Qi
2013-10-18 18:25             ` Pedro Alves
2013-10-19  1:55               ` Yao Qi [this message]
2013-10-25  7:56                 ` Doug Evans
2013-10-16 12:02       ` Pedro Alves

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=5261E638.7030702@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=Hafiz_Abid@mentor.com \
    --cc=Taimoor_Mirza@mentor.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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