Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!ncar!boulder!hartzell
From: hartzell@boulder.Colorado.EDU (George Hartzell)
Newsgroups: comp.unix.ultrix
Subject: Re: ultrix 4.0 cc bug (serious -- varargs)
Keywords: varargs double cc mips compiler
Message-ID: <26794@boulder.Colorado.EDU>
Date: 24 Sep 90 14:28:11 GMT
References: <1990Sep22.175547.3963@cunixf.cc.columbia.edu>
Sender: news@boulder.Colorado.EDU
Reply-To: hartzell@boulder.Colorado.EDU (George Hartzell)
Distribution: usa
Organization: MCD Biology, University of Colorado, Boulder
Lines: 16
In-reply-to: reha@cunixf.cc.columbia.edu (Reha Elci)

In article <1990Sep22.175547.3963@cunixf.cc.columbia.edu>, reha@cunixf (Reha Elci) writes:
>
>For any routine that uses varargs as its input mechanism solely (that is
>va_alist as the only argument) and the first argument is a double varargs
>pulls bad value off of stack:

This is an acknowledged problem on the real MIPS machines (RISC/os),
so I guess that it carries over to the DEC RISC systems.  Their only
suggestion is to use the stdarg mechanism, which works, instead of
varargs.

g.

George Hartzell			                  (303) 492-4535
 MCD Biology, University of Colorado-Boulder, Boulder, CO 80309
hartzell@Boulder.Colorado.EDU           ..!ncar!boulder!hartzell