Hi, resuming this conversation about external objdump,
On 10.08.2013 21:47, Richard Henderson wrote:
> On 08/10/2013 06:53 AM, Max Filippov wrote:
>> On Sat, Aug 10, 2013 at 8:42 PM, Richard Henderson wrote:
>>> On 08/10/2013 05:45 AM, Peter Maydell wrote:
Well, it depends. If we're going to
On Fri, Aug 9, 2013 at 7:19 PM, Richard Henderson wrote:
> We have one host platform (aarch64), and three target platforms
> (openrisc, unicore32, xtensa) with no built-in disassembly support,
> thanks largely to gplv3 silliness.
>
> Here's a first-cut at handling these cases with an external tool
On 08/10/2013 06:53 AM, Max Filippov wrote:
> On Sat, Aug 10, 2013 at 8:42 PM, Richard Henderson wrote:
>> On 08/10/2013 05:45 AM, Peter Maydell wrote:
>>> Well, it depends. If we're going to dump all the in-tree
>>> disassemblers and always use an external objdump, that's fine.
>>
>> It's temptin
On Sat, Aug 10, 2013 at 8:42 PM, Richard Henderson wrote:
> On 08/10/2013 05:45 AM, Peter Maydell wrote:
>> Well, it depends. If we're going to dump all the in-tree
>> disassemblers and always use an external objdump, that's fine.
>
> It's tempting, given that the only internal disassemblers that
On 08/10/2013 05:45 AM, Peter Maydell wrote:
> Well, it depends. If we're going to dump all the in-tree
> disassemblers and always use an external objdump, that's fine.
It's tempting, given that the only internal disassemblers that
are not missing opcodes are for the extinct cpus.
r~
On 10 August 2013 11:22, Claudio Fontana wrote:
> On Sat, Aug 10, 2013 at 11:16 AM, Peter Maydell
> wrote:
>> On 9 August 2013 20:19, Richard Henderson wrote:
>>> We have one host platform (aarch64), and three target platforms
>>> (openrisc, unicore32, xtensa) with no built-in disassembly suppor
On Sat, Aug 10, 2013 at 11:16 AM, Peter Maydell
wrote:
> On 9 August 2013 20:19, Richard Henderson wrote:
>> We have one host platform (aarch64), and three target platforms
>> (openrisc, unicore32, xtensa) with no built-in disassembly support,
>> thanks largely to gplv3 silliness.
>
> FWIW, there
On 9 August 2013 20:19, Richard Henderson wrote:
> We have one host platform (aarch64), and three target platforms
> (openrisc, unicore32, xtensa) with no built-in disassembly support,
> thanks largely to gplv3 silliness.
FWIW, there's an aarch64 BSD disassembler available as part
of vixl: https:
Hi Richard,
On Sat, Aug 10, 2013 at 3:19 AM, Richard Henderson wrote:
> We have one host platform (aarch64), and three target platforms
> (openrisc, unicore32, xtensa) with no built-in disassembly support,
> thanks largely to gplv3 silliness.
Thank you for doing this for or32.
>
> Here's a firs
We have one host platform (aarch64), and three target platforms
(openrisc, unicore32, xtensa) with no built-in disassembly support,
thanks largely to gplv3 silliness.
Here's a first-cut at handling these cases with an external tool.
The qemu-produced dump file contains just a hex dump of bytes, an
10 matches
Mail list logo