From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mukesh Rathor Subject: Re: ATT/GAS syntax manual Date: Tue, 27 Jul 2010 19:28:46 -0700 Message-ID: <20100727192846.0e7b7c07@mantra.us.oracle.com> References: <20100727125527.3b79c6d8@mantra.us.oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: "Xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Tue, 27 Jul 2010 21:17:52 +0100 Keir Fraser 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