> On 10 May 2024, at 7:56 PM, Arnaldo Carvalho de Melo wrote:
>
> On Thu, May 09, 2024 at 10:56:23PM +0530, Athira Rajeev wrote:
>>
>>
>>> On 7 May 2024, at 3:05 PM, Christophe Leroy
>>> wrote:
>>>
>>>
>>>
>>> Le 06/05/2024 à 14:19, Athira Rajeev a écrit :
Add support to capture
On Thu, May 09, 2024 at 10:56:23PM +0530, Athira Rajeev wrote:
>
>
> > On 7 May 2024, at 3:05 PM, Christophe Leroy
> > wrote:
> >
> >
> >
> > Le 06/05/2024 à 14:19, Athira Rajeev a écrit :
> >> Add support to capture and parse raw instruction in objdump.
> >
> > What's the purpose of using
On Thu, May 9, 2024 at 10:27 AM Athira Rajeev
wrote:
>
>
>
> > On 7 May 2024, at 3:05 PM, Christophe Leroy
> > wrote:
> >
> >
> >
> > Le 06/05/2024 à 14:19, Athira Rajeev a écrit :
> >> Add support to capture and parse raw instruction in objdump.
> >
> > What's the purpose of using 'objdump'
> On 7 May 2024, at 3:05 PM, Christophe Leroy
> wrote:
>
>
>
> Le 06/05/2024 à 14:19, Athira Rajeev a écrit :
>> Add support to capture and parse raw instruction in objdump.
>
> What's the purpose of using 'objdump' for reading raw instructions ?
> Can't they be read directly without
Le 06/05/2024 à 14:19, Athira Rajeev a écrit :
> Add support to capture and parse raw instruction in objdump.
What's the purpose of using 'objdump' for reading raw instructions ?
Can't they be read directly without invoking 'objdump' ? It looks odd to
me to use objdump to provide readable
On Mon, May 6, 2024 at 5:21 AM Athira Rajeev
wrote:
>
> Add support to capture and parse raw instruction in objdump.
> Currently, the perf tool infrastructure uses "--no-show-raw-insn" option
> with "objdump" while disassemble. Example from powerpc with this option
> for an instruction address
Add support to capture and parse raw instruction in objdump.
Currently, the perf tool infrastructure uses "--no-show-raw-insn" option
with "objdump" while disassemble. Example from powerpc with this option
for an instruction address is:
Snippet from:
objdump --start-address= --stop-address= -d