Path: utzoo!news-server.csri.toronto.edu!rutgers!rochester!pt.cs.cmu.edu!o.gp.cs.cmu.edu!spot From: spot@CS.CMU.EDU (Scott Draves) Newsgroups: comp.arch Subject: Re: register save Message-ID: Date: 12 Mar 91 19:01:22 GMT References: <3219@crdos1.crd.ge.COM> <12234@pt.cs.cmu.edu> <7403@mentor.cc.purdue.edu> <12269@pt.cs.cmu.edu> <1353@ncis.tis.llnl.gov> <1991Mar12.115845.20736@watdragon.waterloo.edu> Sender: netnews@cs.cmu.edu (USENET News Group Software) Organization: School of Computer Science, Carnegie Mellon University Lines: 22 In-Reply-To: ccplumb@rose.uwaterloo.ca's message of 12 Mar 91 11:58:45 GMT In article <1991Mar12.115845.20736@watdragon.waterloo.edu> ccplumb@rose.uwaterloo.ca (Colin Plumb) writes: Well, I can live with 4 parameters as long as you don't want them to fit in one register each. If you write graphics code, you pass things like 3-vectors (3 registers), basis matrices (9 registers), affine transformations (12) and bicubic patches (16) around. In integers, you often pass rectangle boundaries (4 registers) around. you are almost certainly passing *pointers* to these arrays and matrices around. at least i hope you are... In general, I'd like to suggest that asking the hardware to enforce coding style is like killing ants with a sledgehammer. it's not enforcing anything, it just runs faster if you use its style. -- christianity is stupid Scott Draves communism is good spot@cs.cmu.edu give up