Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!cs.utexas.edu!rutgers!dptg!att!cbnews!mveao
From: mveao@cbnews.ATT.COM (eric.a.olson)
Newsgroups: comp.lang.c
Subject: Re: address of register variables
Message-ID: <9389@cbnews.ATT.COM>
Date: 6 Sep 89 22:44:22 GMT
References: <10809@riks.csl.sony.co.jp>
Reply-To: mveao@cbnews.ATT.COM (eric.a.olson,54242,wi,1f018,508 374 5626)
Organization: AT&T Bell Laboratories
Lines: 13

>>> What if x is in a register?

    Yeah.  What if?  I realize that registers might not have an
    adress that can be taken, but why should that make taking its
    address illegal rather than implementation-dependent?

    I thought that 'register' storage class was supposed to be used
    as a hint to the compiler that the variable would be heavily used and to
    put it in a register if possible.  This concept is not *necessarily*
    at conflict with 'please take the address of this variable'.

						eric olson
						eao@mvuxq.att.com