Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!uunet!stanford.edu!morrow.stanford.edu!pangea.Stanford.EDU!farrell
From: farrell@pangea.Stanford.EDU (Phil Farrell)
Newsgroups: comp.unix.ultrix
Subject: Re: Problems using <varargs.h>
Message-ID: <1991May9.190852.26769@morrow.stanford.edu>
Date: 9 May 91 19:08:52 GMT
References: <1991May8.203720.6846@ux1.cso.uiuc.edu>
Sender: news@morrow.stanford.edu (News Service)
Organization: Stanford Univ. Earth Sciences
Lines: 21

In article <1991May8.203720.6846@ux1.cso.uiuc.edu> cs433aw@ux1.cso.uiuc.edu (Chris Houck) writes:
>Hi, I'm getting some really weird behavior with using the <varargs.h> package
>under Ultrix 4.1.   I'm trying to run the following program --- when the
>size of structure xxx is 12 or less I get the normal behavior, but when I
>increase xxx to size 16 (by uncommenting the "int d;" line) I don't get
>the correct values for the data I try to read with va_arg().

Well, I think you need to get on the phone to DEC Ultrix support and 
request the "ULTRIX XPG3 Upgrade" tape.  I do not have the tape, but 
I have the DEC document entitled "ULTRIX/UWS Version 4.1 XPG3 Upgrade",
DEC order # AA-PE9UA-TE, which states:
	"On RISC platforms, the default system C compiler does not 
	correctly handle the varargs calling sequence when structures
	are passed.  However, pointers, integers, and floating point
	numbers are handled correctly.  The ULTRIX/UWS Version 4.1
	XPG3 Upgrade release includes a new version of the C compiler
	that corrects this problem."

-Phil Farrell, Computer Systems Manager
Stanford University School of Earth Sciences
farrell@pangea.stanford.edu