Re: A89: the a68k assembler and how it makes machine code


[Prev][Next][Index][Thread]

Re: A89: the a68k assembler and how it makes machine code




Something like that. Only it has to insert codes for the registers, the
length (.b .w .l), etc. Much of that Programmer's Reference Manual that
Motorola sends you is information for people who are making compiles...

-Zero
President of Mogsoft, Inc.

----- Original Message -----
From: mhlandry <mhlandry@bellsouth.net>
To: <assembly-89@lists.ticalc.org>
Sent: Tuesday, November 09, 1999 2:51 PM
Subject: Re: A89: the a68k assembler and how it makes machine code


>
> Just guessing here, but I am willing to bet that the assembler has some
> sort of table, it gets your code, and looks for the corresponding value
> in the table.  Someone please correct me on this if I am wrong!
>      - Matt
>
> mxpxfifws@yahoo.com wrote:
> >
> > What I want to know is how the assembler gets the hex code for
instructions that you write
> > down.  Like how does "4e444e750000" stand for "Trap #4" and then "rts"?
> > Bryan
> >
> > > ** Original Subject: re: Re: A89: the a68k assembler and how it makes
machine code
> > > ** Original Sender: Zoltan Kocsi <zoltan@bendor.com.au>
> > > ** Original Date: Tue,  9 Nov 1999 18:20:52 +1100 (EST)
> >
> > > ** Original Message follows...
> >
> > >
> > > > ok, I ordered the documentation.  hopefully, it will clear up any
problems I have.  Oh
> > yeah,
> > >  > this is probably in the docs, but I can't wait to find out:  how do
ram calls work?  and
> > why
> > >  > can't as92 do them yet?  j/w.  Thanks
> > >
> > > I am not sure that I understand your problem. The way an assembler
> > > works is fairly simple. The documentation you ordered, however, will
> > > not explain that. Instead, it will have detailed explanations on the
> > > various m68k instructions, their bit-patterns (for not too many
> > > instruction has a fixed hex code) and other aspects of the 68000 CPU,
> > > such as bus timing, electrical characteristics, instruction execution
> > > times etc.
> > >
> > > They will *not* explain anything that is TI89 or TI92 specific or
> > > specific to your assembler. They will *not* explain assembler
> > > directives, nor library handling. You won't get any info on label
> > > calculations, relocation techniques and alike.
> > > In fact, Motorola tells you what the chip does when it reads certain
> > > bit patterns from its memory. It will give you absolutely no help with
> > > regards to generating those bit patterns from an assembly source.
> > > The documentation that comes with your assembler is supposed to cover
> > > that area.
> > >
> > > It might be wiser if you tried to explain what you actually want
> > > to know or what your actual problem is.
> > >
> > > Regards,
> > >
> > > Zoltan
> >
> > >** --------- End Original Message ----------- **
> >
> > >
> >
> > Download NeoPlanet at http://www.neoplanet.com
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Bid and sell for free at http://auctions.yahoo.com
>



References: