From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: Re: ATT/GAS syntax manual
Date: Tue, 27 Jul 2010 19:28:46 -0700 [thread overview]
Message-ID: <20100727192846.0e7b7c07@mantra.us.oracle.com> (raw)
In-Reply-To: <C874FD80.4163%keir.fraser@eu.citrix.com>
On Tue, 27 Jul 2010 21:17:52 +0100
Keir Fraser <keir.fraser@eu.citrix.com> wrote:
> I don't think there is such a thing. There are general rules for
> writing operands, effective addresses, and ordering of operands of
> course. If I had a specific issue with a particular instruction then
> I would construct an example in machine code using .byte directive in
> a .S file, gcc/gas it to an object file, and the objdump -d that file
> to see the AT&T syntax for the instruction.
>
> -- Keir
Ah, I thought so. I have similar tricks, I usually use gdb to toggle
syntax between AT&T and INTEL, and figure out that way.
thanks,
Mukesh
prev parent reply other threads:[~2010-07-28 2:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 19:55 ATT/GAS syntax manual Mukesh Rathor
2010-07-27 20:17 ` Keir Fraser
2010-07-28 2:28 ` Mukesh Rathor [this message]
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=20100727192846.0e7b7c07@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=Xen-devel@lists.xensource.com \
--cc=keir.fraser@eu.citrix.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 NNTP newsgroup(s).