public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
* Possible bug in objdump?
@ 2002-05-01 19:53 Unix User
  2002-05-01 20:01 ` DJ Delorie
  0 siblings, 1 reply; 2+ messages in thread
From: Unix User @ 2002-05-01 19:53 UTC (permalink / raw)
  To: binutils

Hi,

While disassembling dhry11.c which is part of the
Dhrystone benchmarks version 1.1, objdump seems to
disassemble incorrectly. In particular, objdump deals
with the instructions "rep" and "movs" incorrectly. 

So, I run:
gcc -S dhry11.c -o dhry11.s
gcc -c dhry11.c -o dhry11.o
objdump -d --no-show-raw-insn -r -s dhry11.o >
dhry11.dis

Now, dhry11.s contains the lines:
rep
movsl

The corresponding instructions in the disassembly (in
dhry11.dis) is  emitted on one line as:
4c8:   repz movsl %ds:(%esi),%es:(%edi)

The other instructions are disassembled correctly. So,
my question is: Is this a known bug in objdump and are
there fixes for the bug?

I can include the source file, dhry11.c, if needed.

Thanks

__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Possible bug in objdump?
  2002-05-01 19:53 Possible bug in objdump? Unix User
@ 2002-05-01 20:01 ` DJ Delorie
  0 siblings, 0 replies; 2+ messages in thread
From: DJ Delorie @ 2002-05-01 20:01 UTC (permalink / raw)
  To: anunxusr; +Cc: binutils


> In particular, objdump deals with the instructions "rep" and "movs"
> incorrectly.

"rep" isn't an instruction, it's a prefix.  It belongs with the
following opcode, just like es: or a size override.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2002-05-02  3:01 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-05-01 19:53 Possible bug in objdump? Unix User
2002-05-01 20:01 ` DJ Delorie

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).