Package: binutils Version: 2.17-3 Severity: normal
objdump -d -M intel puts the operands in the Intel order, but still uses the buggy Unixware-compat opcodes. (This affects non-commutative floating point ops with both args on the FP stack, e.g. fsubrp and fsubp are switched in gas's AT&T syntax.) I suggest that this bug compatibility doesn't make any sense in Intel mode, and will just cause problems for people. e.g. the comments in the source for FFFF (http://sourceforge.net/projects/ffff/) document the author's frustration with getting his inline asm FPU code to work. (search for "sahf" in the source; it occurs only in the fpu asm code). It took me all afternoon to find out what was going wrong. After finding the i386 bugs section in the gas info page, I was still misled because I assumed using -M intel would show me the proper disassembly. I should have used ndisasm :( Unlike bug #372528, this is not documented behaviour, AFAICT. I'll reply to that bug with some links to stuff I found useful in finding out what's up with the buggy opcodes. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-1-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages binutils depends on: ii libc6 2.3.6.ds1-7 GNU C Library: Shared libraries binutils recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
