Package: binutils
Version: 2.17-3
Followup-For: Bug #372528

 gas is intentionally bug-compatible with early 386 Unix
compilers/assemblers, which got fsub and fsubr and others switched.
gcc generates code using these buggy opcodes, and inline asm uses it,
so we're stuck with it now, and even amd64 too, unfortunately.  Damn,
you can never get rid of cruft once it starts to accumulate :(

 Unfortunately binutils frobs the opcodes when disassembling with
objdump -M intel -d foo.o, so you can't get binutils to show you
assembly source that corresponds to Intel manuals.  I've reported this
as Debian bug #397545.  ndisasm and ht both work, but don't do a great
job with ELF sections, and seem to diassemble the ELF headers.

here's all the good stuff I've turned up on this subject:
 (as.info.gz)i386-Bugs.
 the comment which begins with "The SystemV/386 SVR3.2 assembler", at
  the top of opcode/i386.h (e.g. 
http://opengrok.creo.hu/dragonfly/xref/src/contrib/binutils-2.15/include/opcode/i386.h#opcode)
This thread:
 http://gcc.gnu.org/ml/gcc-patches/2000-03/msg00864.html
and another example of this cruft causing headaches:
 http://sources.redhat.com/ml/binutils/1999-10/msg00109.html
 Debian bug #397545
 http://en.wikipedia.org/wiki/X86_assembly_language
 http://www.sesp.cse.clrc.ac.uk/html/SoftwareTools/vtune/users_guide/
(don't eat their bandwidth;  I just found that page with google...)
The instruction VTune instruction reference in vtune proved very
useful, because it has a good menu on the left, and the page for each
opcode makes it clear what the machine codes are in hex, so you can
compare with what your disassembler is showing.  e.g.
http://www.sesp.cse.clrc.ac.uk/html/SoftwareTools/vtune/users_guide/mergedProjects/analyzer_ec/mergedProjects/reference_olh/mergedProjects/instructions/instruct32_hh/vc123.htm
There seem to be several places to find the VTune docs online on
public web servers, so find a mirror if you're going to bookmark it.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to