home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.arch
- Path: sparky!uunet!europa.asd.contel.com!emory!cs.utk.edu!willis1.cis.uab.edu!hyatt
- From: hyatt@cis.uab.edu (Robert Hyatt)
- Subject: Re: RISC assemblers question
- Message-ID: <1992Dec18.221947.8589@cis.uab.edu>
- Organization: University of Alabama at Birmingham
- References: <Dec.17.10.16.36.1992.17493@cadenza.rutgers.edu> <75756@apple.apple.COM>
- Date: Fri, 18 Dec 1992 22:19:47 GMT
- Lines: 25
-
- In article <75756@apple.apple.COM> tim@Apple.COM (Tim Olson) writes:
- >In article <Dec.17.10.16.36.1992.17493@cadenza.rutgers.edu> masticol@cadenza.rutgers.edu (Steve Masticola) writes:
- >
- >|I've met a couple of people who have attempted to write assemblers for
- >|RISC machines, who say that it's a difficult job. Can someone give me
- >|an inkling as to why?
- >
- >From my experience, it's just the opposite. RISC processors tend to
- >have a few simple instruction formats, fixed fields, etc. Also, with
- >the limited number of addressing modes in RISC processors, parsing
- >becomes almost trivial.
- >
-
-
- The problem is that the assembler writer apparently never knows when his
- job is finished..... :^) He/she keeps writing, handling more special
- cases, etc. The final product IS a difficult project. However, I would
- prefer a simple assembler, not one that tries to "think" for me. An
- example is the one from Cray Research. It doesn't "get in the way" of
- my bad (or good) coding practices.
-
-
- --
- !Robert Hyatt Computer and Information Sciences !
- !hyatt@cis.uab.edu University of Alabama at Birmingham !
-