From: peter willy krause <wklux@yahoo.co.uk>
To: Frederic Beuserie <fb@lab21.cs.bitpack.org>,
linux-assembly@vger.kernel.org,
linux-assembly@mlists.in-berlin.de
Subject: Re: ia32 instruction sets
Date: Tue, 27 Jan 2004 10:50:55 +0000 [thread overview]
Message-ID: <200401271051.09387.wklux@yahoo.co.uk> (raw)
In-Reply-To: <m3hdyiwfgz.fsf@lab21.cs.bitpack.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
afaik, no comprehensive ia32 doc wrt att syntax exists but, some more or
less incomplete, 'translations'.
the easiest choice, if sufficient, would be the "nasm" documentation,
which can be generated in almost any commonly used output format.
best,
hp
Am Montag, 26. Januar 2004 21:46 schrieb Frederic Beuserie:
> hi,
>
> i've downloaded the references from intel for ia32/P4 cpus and it
> appears it's not really easy to use it as a "hand" reference (pdf, ...)
>
> did you know a location where there's a comprensive and easily
> browseable reference of ia32 instructions, coupled with the syntax i
> gas use.
>
> thanks.
>
> frederic b.
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-assembly" in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
- --
mail to 'hp' : lx at lxhp . in-berlin . de
http://www.lxhp.in-berlin.de/index-lx.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFAFkKc4A8LYevsFkwRAtsfAKDD6uDUhulBFRgdgaJHoI3nvT2TnQCfTrp+
kvONsTWnpf3uRSTqIMabuTk=
=ph8T
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-01-27 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 21:46 ia32 instruction sets Frederic Beuserie
2004-01-27 10:50 ` peter willy krause [this message]
2004-02-03 6:54 ` explaination needed Vadiraj C S
2004-02-03 7:52 ` Anticipating a Reply
2004-02-03 17:00 ` peter willy krause
2004-02-04 9:47 ` dEAthBloW-wnCia
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=200401271051.09387.wklux@yahoo.co.uk \
--to=wklux@yahoo.co.uk \
--cc=fb@lab21.cs.bitpack.org \
--cc=linux-assembly@mlists.in-berlin.de \
--cc=linux-assembly@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.