This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] Disassembly improvements
- From: Doug Evans <dje at google dot com>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: Pedro Alves <palves at redhat dot com>, "Abid, Hafiz" <Hafiz_Abid at mentor dot com>, "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>, "Mirza, Taimoor" <Taimoor_Mirza at mentor dot com>
- Date: Fri, 25 Oct 2013 00:56:07 -0700
- Subject: Re: [patch] Disassembly improvements
- Authentication-results: sourceware.org; auth=none
- References: <EB3B29AD43CA924DA27099BC85192376E0705106 at EU-MBX-03 dot mgc dot mentorg dot com> <CADPb22RShPCFWpZhgfv6-ZDtSA=6PK+qwVaetth4tKM1LJLnjA at mail dot gmail dot com> <525C02E5 dot 2060601 at redhat dot com> <21085 dot 59640 dot 697075 dot 435874 at ruffy dot mtv dot corp dot google dot com> <525E4596 dot 70503 at codesourcery dot com> <525E81B8 dot 90003 at redhat dot com> <52610BF7 dot 8000605 at codesourcery dot com> <52617D1A dot 6010600 at redhat dot com> <5261E638 dot 7030702 at codesourcery dot com>
On Fri, Oct 18, 2013 at 6:54 PM, Yao Qi <yao@codesourcery.com> wrote:
> 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.
You'll need to add some sort of prefetcher called from a higher level
in the disassembler that knows the memory range being disassembled.