Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site utcsri.UUCP
Path: utzoo!utcsri!greg
From: greg@utcsri.UUCP (Gregory Smith)
Newsgroups: comp.lang.c
Subject: Re: Register arguments (was: Order of registers)
Message-ID: <4353@utcsri.UUCP>
Date: Fri, 13-Mar-87 12:51:51 EST
Article-I.D.: utcsri.4353
Posted: Fri Mar 13 12:51:51 1987
Date-Received: Sat, 14-Mar-87 01:21:33 EST
References: <902@cullvax.UUCP>
Reply-To: greg@utcsri.UUCP (Gregory Smith)
Organization: CSRI, University of Toronto
Lines: 22
Summary: 'register arg' does not specify calling convention

In article <902@cullvax.UUCP> drw@cullvax.UUCP writes:
>Well, reading section 3.5.3.3, 'register' is specifically allowed for
>function arguments, and all other storage class specifiers are
>specifically forbidden.  I presume that this means that it is
>significant in matching, probably so the compiler can pass the
>argument via a register.  Sigh!  Another ambiguity in X3J11.
>
The same specification (re storage class for func arguments) is made
in K&R Appendix section 10.1, where it means nothing of the sort.

[ I don't have an ANSI draft, but if the above section is your only
support, you must be mistaken ]

I would think it would be up to the implementors of a compiler/load/runtime
environment to make sure that arguments expected in registers are
passed in registers.

>Dale Worley		Cullinet Software
-- 
----------------------------------------------------------------------
Greg Smith     University of Toronto      UUCP: ..utzoo!utcsri!greg
Have vAX, will hack...