home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!snorkelwacker.mit.edu!ai-lab!zurich.ai.mit.edu!gjr
- From: gjr@zurich.ai.mit.edu (Guillermo J. Rozas)
- Newsgroups: comp.arch
- Subject: Re: why no register + register addressing mode in R3000
- Date: 10 Nov 92 11:12:23
- Organization: M.I.T. Artificial Intelligence Lab.
- Lines: 17
- Message-ID: <GJR.92Nov10111223@chamarti.ai.mit.edu>
- References: <18938@ucdavis.ucdavis.edu> <endecotp.721329802@cs.man.ac.uk>
- Reply-To: gjr@zurich.ai.mit.edu
- NNTP-Posting-Host: chamartin.ai.mit.edu
- In-reply-to: endecotp@cs.man.ac.uk's message of 9 Nov 92 17:23:22 GMT
-
- In article <endecotp.721329802@cs.man.ac.uk> endecotp@cs.man.ac.uk (PB Endecott (PhD SFurber)) writes:
-
- | Of course for a load, you do have two read ports available. Would anyone
- | consider an architecture with non-symetrical addressing modes, where loads
- | can do register+constant or register+register, but stores can do
- | register+constant only?
- |
- | Another feature that some processors have and others don't is
- | auto-indexing. During loads, this requires an extra write port (or an
- | extra cycle) to put the modified value back in the register; but during
- | stores the write port is not used for data. So how about an architecture
- | with autoindexing for stores but not for loads ?
-
- The HP-PA (1.1) architecture has indexed integer loads but no indexed
- integer stores. It has both indexed floating-point loads and stores.
- It has auto-increment on both loads and stores.
-
-