public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Vincent Rubiolo <vincent.rubiolo@st.com>
To: binutils@sources.redhat.com
Cc: nickc@redhat.com
Subject: Re: [arnm-elf-objdump] Can't use two -M flags for disassembler (-Mforce-thumb and -Mreg-names-raw)
Date: Mon, 14 Jul 2003 14:48:00 -0000	[thread overview]
Message-ID: <3F136B7B.6090201@st.com> (raw)
In-Reply-To: <H0000cba18680191.1057939164.eux100.sgp.st.com@MHS>

Hello,

Sorry for the delay.
I am using binutils 2.14 and also a snapshot from the 19th of June.

The problem arises when I try to inspect THUMB code generated by ADS 
(interworking enabled). I have to use -Mforce-thumb, otherwise everything is 
seen as ARM code.
Here are the outputs (from a C file compiled as THUMB):


% arm-elf-objdump -d ADS_file -Mforce-thumb
  	1002444:       b510            push    {r4, lr}

% arm-elf-objdump -d ADS_file -Mforce-thumb -Mreg-names-raw
	1002444:       2400b510        strcs   r11, [r0], -#1296

The first one is correct.
Pb then, as it seems that the -Mreg-names-raw turned off the -Mforce-thumb 
option on the second attempt.


Also, on ARM code, it works just as you stated:
% arm-elf-objdump -d ADS_file
	1000150:       e1a0f00c        mov     pc, ip

% arm-elf-objdump -d ADS_file -Mreg-names-raw
	1000150:       e1a0f00c        mov     r15, r12

% arm-elf-objdump -d ADS_file -Mreg-names-raw -Mforce-thumb
	1000150:       e1a0f00c        blx     100c494 <$b+0x36>


Hope that clarify the situation. Thing is I am operating the opposite way 
(looking at THUMB code).

Regards,

Vincent


nickc@redhat.com wrote:

> Hi Vincent,
> 
> 
>>This may be very stupid but I am unable to use both flags
>>-Mreg-names-raw and -Mforce-thumb at the same time (arm-elf-objdump)
> 
> 
> Which version of binutils are you using ?
> 
> It appears to work for me (using the current CVS sources and the 2.14
> release):
> 
>   % objdump -d mov.o
>  
>      0:   e1a0e00f        mov     lr, pc
> 
>   % objdump -d -Mreg-names-raw nop.o
>  
>      0:   e1a0e00f        mov     r14, r15
> 
>    % objdump -d -Mreg-names-raw -Mforce-thumb nop.o
>  
>      0:   e00f            b       22 <fred+0x22>
>      2:   e1a0            b       346 <fred+0x346>
>  
> Cheers
>         Nick
> 

  parent reply	other threads:[~2003-07-14 14:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-10 15:38 Vincent Rubiolo
2003-07-11 14:35 ` Nick Clifton
     [not found] ` <H0000cba18680191.1057939164.eux100.sgp.st.com@MHS>
2003-07-14 14:48   ` Vincent Rubiolo [this message]
2003-07-17 14:44     ` Nick Clifton
     [not found]     ` <H0000cba186df243.1058453251.eux100.sgp.st.com@MHS>
2003-07-17 15:31       ` Vincent Rubiolo
2003-07-17 17:02         ` Nick Clifton
2003-07-17 18:39           ` Daniel Jacobowitz
2003-07-18 11:34             ` Nick Clifton
     [not found]             ` <H0000cba187217e5.1058853947.eux100.sgp.st.com@MHS>
2003-07-23  6:39               ` [arnm-elf-objdump] Can't use two -M flags for disassembler [SOLVED] Vincent Rubiolo
2003-07-18  8:05           ` [arnm-elf-objdump] Can't use two -M flags for disassembler (-Mforce-thumb and -Mreg-names-raw) Andreas Schwab

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=3F136B7B.6090201@st.com \
    --to=vincent.rubiolo@st.com \
    --cc=binutils@sources.redhat.com \
    --cc=nickc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).