salomon@ccu.umanitoba.ca (Dan Salomon) (03/14/91)
I teach a compiler course in which the student's projects generate
SPARC code. To generate correct SPARC code the students need a
description of the SPARC architecture. We have been using the SUN
manual 800-1399-08 "The SPARC Architecture Manual".
The peculiar thing is that this manual is out of print. Every
year I get permission from SUN to photocopy my dog-eared copy
for the students.
Does anyone know what is going on with this manual?
Is there some replacement that I and my SUN sales rep. are unaware of?
Isn't the SPARC supposed to be an open architecture with a standard
description somewhere?
--
Dan Salomon -- salomon@ccu.UManitoba.CA
Dept. of Computer Science / University of Manitoba
Winnipeg, Manitoba, Canada R3T 2N2 / (204) 275-6682
--
Send compilers articles to compilers@iecc.cambridge.ma.us or
{ima | spdcc | world}!iecc!compilers. Meta-mail to compilers-request.ken@gatech.edu (Ken Seefried iii) (03/15/91)
In article <1991Mar14.031322.12128@ccu.umanitoba.ca> salomon@ccu.umanitoba.ca (Dan Salomon) writes: > [Are Sparc architecture references available? Sun's is out of print.] I duuno about the Sun manual, but it seems to me that you should be able to get the equivalent thing from one of the houses that fabs SPARC chips, such as Cypress or Fujitsu. I would also suspect that Solbourne has such a manual. -- ken seefried iii ken@dali.cc.gatech.edu -- Send compilers articles to compilers@iecc.cambridge.ma.us or {ima | spdcc | world}!iecc!compilers. Meta-mail to compilers-request.
mslater@cup.portal.com (Michael Z Slater) (03/15/91)
>I teach a compiler course in which the student's projects generate >SPARC code. To generate correct SPARC code the students need a >description of the SPARC architecture. We have been using the SUN >manual 800-1399-08 "The SPARC Architecture Manual". > >The peculiar thing is that this manual is out of print. Every >year I get permission from SUN to photocopy my dog-eared copy >for the students. > >Does anyone know what is going on with this manual? >Is there some replacement that I and my SUN sales rep. are unaware of? >Isn't the SPARC supposed to be an open architecture with a standard >description somewhere? The responsibility for producing the architecture manual has been transferred to SPARC International. I suspect that the manual is out of print because the version 8 manual has been expected real soon now for some time. The new version should be available from SI very soon now. You might try contacting the SPARC International communications manager, David Fickes, at dfickes@sparc.com, or 415/321-8692.
vhs@britesun.radig.de (Volker Herminghaus-Shirai) (03/17/91)
dali!ken@gatech.edu (Ken Seefried iii) writes: >In article <1991Mar14.031322.12128@ccu.umanitoba.ca> salomon@ccu.umanitoba.ca (Dan Salomon) writes: >> [Are Sparc architecture references available? Sun's is out of print.] >I duuno about the Sun manual, but it seems to me that you should be >able to get the equivalent thing from one of the houses that fabs >SPARC chips, such as Cypress or Fujitsu. I would also suspect that >Solbourne has such a manual. For instance, you can go for the Cypress Semiconductor's Reference Manual for the CY7C601/CY7C611. I don't know where you can get it in the US since I live in Germany... Volker -- Volker Herminghaus-Shirai (vhs@britesun.radig.de) panic: 80x86! Trying to vomit...
mwb2c@euclid.acc.Virginia.EDU (Mark W. Brunkhart) (03/20/91)
In article <1991Mar14.031322.12128@ccu.umanitoba.ca> salomon@ccu.umanitoba.ca (Dan Salomon) writes: > [Are Sparc architecture references available? Sun's is out of print.] I had a lot of trouble getting a SPARC manual out of SUN this winter. They just published the SPARC Architecture Manual (Version 8) on December 11 although they've been referencing it in their literature for some time. Although many of the retailers might not have this manual yet, it is Part No: 800-1399-12. After I finally found someone who knew what the manual was, no less that it did exist, they were nice enough to send me a copy free. FYI: SUN (415) 960-1300 Sun Microsystems, Inc. 2550 Garcia Avenue Mountain View, CA 94043 Hope this helps, Mark Brunkhart mwb2c@virginia.edu
salomon@ccu.umanitoba.ca (Dan Salomon) (03/21/91)
In article <1991Mar19.214110.23955@murdoch.acc.Virginia.EDU> mwb2c@euclid.acc.Virginia.EDU (Mark W. Brunkhart) writes: > >I had a lot of trouble getting a SPARC architecture manual out of SUN >this winter. [...] After I finally found >someone who knew what the manual was, no less that it did exist, >they were nice enough to send me a copy free. I know the feeling. The toughest thing is trying to explain the difference between the assembler language manual, which is easy to get, and the architecture manual. One of the problems is that these days, only compiler writers need architecture manuals. -- Dan Salomon -- salomon@ccu.UManitoba.CA Dept. of Computer Science / University of Manitoba Winnipeg, Manitoba, Canada R3T 2N2 / (204) 275-6682
larus@primost.cs.wisc.edu (James Larus) (03/21/91)
In article <1991Mar20.195012.24448@ccu.umanitoba.ca>, salomon@ccu.umanitoba.ca (Dan Salomon) writes: |> In article <1991Mar19.214110.23955@murdoch.acc.Virginia.EDU> mwb2c@euclid.acc.Virginia.EDU (Mark W. Brunkhart) writes: |> > |> >I had a lot of trouble getting a SPARC architecture manual out of SUN |> >this winter. [...] After I finally found |> >someone who knew what the manual was, no less that it did exist, |> >they were nice enough to send me a copy free. |> |> I know the feeling. The toughest thing is trying to explain the |> difference between the assembler language manual, which is easy to |> get, and the architecture manual. One of the problems is that these |> days, only compiler writers need architecture manuals. |> -- Try hitting up your Sun salesperson. After several years of trying to make a profit off this document, some genius at Sun finally realized that there is more money hardware and software than paper. After several years of effort, the Computer Sciences Department at UW is now the proud owner of 3 (three!) architecture manuals. /Jim