Xref: utzoo comp.arch:6268 comp.lang.c:12374 Path: utzoo!utgpu!water!watmath!clyde!att!rutgers!ucsd!ucsdhub!esosun!seismo!uunet!ateng!chip From: chip@ateng.uucp (Chip Salzenberg) Newsgroups: comp.arch,comp.lang.c Subject: Re: separate integer and float registers Message-ID: <1988Sep6.115809.21415@ateng.uucp> Date: 6 Sep 88 15:58:08 GMT References: <2724@wright.mips.COM> <56@radix> <705@bacchus.DEC.COM> Reply-To: chip@ateng.UUCP (Chip Salzenberg) Followup-To: comp.lang.c Organization: A T Engineering, Tampa, FL Lines: 17 [ this is becoming language-specific; followups are directed to comp.lang.c ] According to alverson@decwrl.dec.com (Robert Alverson): >One unfortunate aspect of separate fp and integer registers shows up >with varargs parameter passing. Given that you want to pass parameters >in registers in optimized code, it seems that any call to a varargs >procedure must be detected, and any fp parameters passed in integer >registers. No. Fp variables may reside in a separate set of registers and be found there by a varargs function. This approach requires compiler support for noticing the actual type of each varargs parameter instead of just its size; but that's why we have varargs (or stdarg) in the first place. -- Chip Salzenberg or A T Engineering My employer may or may not agree with me. The urgent leaves no time for the important.