Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!noose.ecn.purdue.edu!mentor.cc.purdue.edu!l.cc.purdue.edu!cik From: cik@l.cc.purdue.edu (Herman Rubin) Newsgroups: comp.arch Subject: Re: What *should* architectural pointers point at? Message-ID: <2504@l.cc.purdue.edu> Date: 2 Sep 90 12:37:36 GMT References: <0887@sheol.UUCP> <11192@celit.fps.com> Organization: Purdue University Statistics Department Lines: 15 In article <11192@celit.fps.com>, dave@fps.com (Dave Smith) writes: > In article <3318@awdprime.UUCP> tif@reed.UUCP (Paul Chamberlain/32767) writes: ..................... > This bit addressing stuff is all fine and well, but it seems like a lot of > extra baggage to carry around for a little bit-twiddling every now and then. > Why not just have operations that will return the nth bit? But what if k bits, starting from the n-th bit, are wanted? This is not all that uncommon, and may be needed frequently, including supercomputers. -- Herman Rubin, Dept. of Statistics, Purdue Univ., West Lafayette IN47907 Phone: (317)494-6054 hrubin@l.cc.purdue.edu (Internet, bitnet) {purdue,pur-ee}!l.cc!cik(UUCP)