Re: Guidelines for instruction set design?

"BartC" <bartc@freeuk.com>
Tue, 05 May 2009 21:13:50 GMT

          From comp.compilers

Related articles
[2 earlier articles]
Re: Guidelines for instruction set design? kamalpr@gmail.com (2009-05-03)
Re: Guidelines for instruction set design? gneuner2@comcast.net (George Neuner) (2009-05-03)
Re: Guidelines for instruction set design? hsheboul@gmail.com (Hasan Alsheboul) (2009-05-04)
Re: Guidelines for instruction set design? cyril.cressent@gmail.com (2009-05-04)
Re: Guidelines for instruction set design? torbenm@pc-003.diku.dk (2009-05-04)
Re: Guidelines for instruction set design? gah@ugcs.caltech.edu (glen herrmannsfeldt) (2009-05-05)
Re: Guidelines for instruction set design? bartc@freeuk.com (BartC) (2009-05-05)
Re: Guidelines for instruction set design? gneuner2@comcast.net (George Neuner) (2009-05-05)
Re: Guidelines for instruction set design? walter@bytecraft.com (Walter Banks) (2009-05-06)
Re: Guidelines for instruction set design? gmt@cs.arizona.edu (2009-05-06)
Re: Guidelines for instruction set design? dot@dotat.at (Tony Finch) (2009-05-07)
Re: Guidelines for instruction set design? gneuner2@comcast.net (George Neuner) (2009-05-10)
Re: Guidelines for instruction set design? toby@telegraphics.com.au (toby) (2009-05-10)
[7 later articles]
| List of all articles for this month |

From: "BartC" <bartc@freeuk.com>
Newsgroups: comp.compilers
Date: Tue, 05 May 2009 21:13:50 GMT
Organization: Compilers Central
References: 09-05-020
Keywords: design, architecture
Posted-Date: 06 May 2009 05:57:23 EDT

<cyril.cressent@gmail.com> wrote in message news:09-05-020@comp.compilers...


> - 32-bits RISC, implemented in a FPGA
> - Big Endian
> - Multipurpose, though it has a MULAC module for signal processing
> - Word adressable
>
> - $R0..15: 32-bits general purpose registers.
>
> - $C0..15: 32-bits "Counter" registers.


(I always have trouble with special purpose registers (eg. Motorola 68K with
Data and Address registers). Things are much easier when all registers are
orthogonal.)


> They can be used to load a
> constant or an address and to do indirect memory addressing.


So you don't have direct memory addressing, but have to load the address
into $Cn first and access that indirectly?


I'm not familiar with how LCC works; why can't a single Load or Store
operation map into two or more of your instructions (load address then
indirect access)?


--
Bart



Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.