This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: where can I find the assebly language manual used in the coding..
- From: Nick Garnett <nickg at ecoscentric dot com>
- To: Jonathan Larmour <jifl at eCosCentric dot com>
- Cc: Sivakamesh Thota <thota at cosmic dot utah dot edu>,Michael Anburaj <embeddedeng at hotmail dot com>,ecos-discuss at sources dot redhat dot com
- Date: 16 Jul 2003 09:03:52 +0100
- Subject: Re: [ECOS] where can I find the assebly language manual used in the coding..
- References: <Pine.LNX.4.44.0307151247280.28037-100000@bessie.cosmic.utah.edu><3F148682.1000600@eCosCentric.com>
Jonathan Larmour <jifl@eCosCentric.com> writes:
> Sivakamesh Thota wrote:
> > On Tue, 15 Jul 2003, Michael Anburaj wrote:
> >
> >>Hi Kamesh,
> >>
> >>Which procssor or platform?
> > sorry i forgot to mention..
> > AMD or i386 architecture
>
> Obviously you can also look at the "info gas" stuff as Gary says, but
> general stuff about the IA32 instruction set is at e.g. for pentium
> http://developer.intel.com/design/intarch/pentium/docs_pentium.htm
> and similarly you can hunt around the AMD site.
>
Those pages would not be a great help since GAS implements the AT&T
syntax rather than the Intel syntax. However to anyone familiar with
Intel syntax, AT&T syntax should be easy to pick up -- I certainly
never had any difficulty.
The main differences are:
- source and destination operands are in reverse order.
- The size of a transfer is encoded as a "b", "w" or "l" suffix on the
opcode, not inferred from the operands.
- The general syntax of addressing modes is offset(base_reg,index_reg,scale)
with elements omitted if they are not needed.
- Some of the more obscure opcodes are named slightly differently.
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com/ The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss