From: Bernd Jendrissek <berndj@prism.co.za>
To: "Allan B. Cruse" <cruse@cs.usfca.edu>
Cc: binutils@sources.redhat.com, hjl@lucon.org, gcc@gcc.gnu.org,
libc-alpha@sources.redhat.com
Subject: Re: PATCH: Fix i386 disassembler with index == 0x4 in SIB (Re: objdump bug-report)
Date: Fri, 14 Jan 2005 07:32:00 -0000 [thread overview]
Message-ID: <20050114072330.GC23382@prism.co.za> (raw)
In-Reply-To: <20050114061022.50A1C21A49@nexus.cs.usfca.edu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, Jan 13, 2005 at 10:10:22PM -0800, Allan B. Cruse wrote:
> whereas only those having an intimate acquaintance with Intel's
> documentation would be able to quickly know that " movl (%esi,2),%eax
> " does NOT scale the index-register, contrary to what the syntax
> indicates.
For compulsive bit-fiddlers, it might make sense to allow (%esi,2,) just
like gas already allows (?) (,1,%ebx).
> and to decrypt secret messages someone might have hidden inside a
> code-stream.
So who's writing up a patch to fingerprint binaries with "GAS and GNU
rulez!"? :-)
- --
Seen in comp.lang.c:
> cody wrote:
>> The problem is that i believe that my assertions are correct.
> Yes, that is a problem.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQFB53Nq/FmLrNfLpjMRAha4AJwM4oiuloCfULekZ5Sih3HpyeKpMgCgh/pa
c9sbSZ/fDeaosyolljLBpE4=
=qgJj
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-01-14 7:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 6:11 Allan B. Cruse
2005-01-14 7:32 ` Bernd Jendrissek [this message]
2005-01-14 17:19 ` E. Weddington
-- strict thread matches above, loose matches on Subject: below --
2005-01-13 17:42 Allan B. Cruse
[not found] <20050111210753.0C8CB219E0@nexus.cs.usfca.edu>
2005-01-12 19:10 ` H. J. Lu
2005-01-13 3:44 ` Alan Modra
2005-01-13 17:09 ` H. J. Lu
2005-01-13 17:27 ` H. J. Lu
2005-01-14 0:06 ` Alan Modra
2005-01-14 0:27 ` H. J. Lu
2005-01-14 0:59 ` Alan Modra
2005-01-14 21:49 ` H. J. Lu
2005-01-14 7:04 ` Bernd Jendrissek
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=20050114072330.GC23382@prism.co.za \
--to=berndj@prism.co.za \
--cc=binutils@sources.redhat.com \
--cc=cruse@cs.usfca.edu \
--cc=gcc@gcc.gnu.org \
--cc=hjl@lucon.org \
--cc=libc-alpha@sources.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).