Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!elroy.jpl.nasa.gov!sdd.hp.com!news.cs.indiana.edu!nstn.ns.ca!uupsi!lupine!rfg
From: rfg@NCD.COM (Ron Guilmette)
Newsgroups: comp.lang.c++
Subject: Re: stdarg.h C++ 2.1 AT&T on sparc
Message-ID: <5793@lupine.NCD.COM>
Date: 30 May 91 22:28:43 GMT
References: <1991May22.144659.13993@info-sparc1.info.ucl.ac.be>
Organization: Network Computing Devices, Inc., Mt. View, CA
Lines: 25

In article <1991May22.144659.13993@info-sparc1.info.ucl.ac.be> martou@fynu.ucl.ac.be (Jean-Luc Martou) writes:
>Hello!
>
>We have a big problem concerning the file <stdarg.h> with the AT&T C++ 2.1
>translator we have ported on SPARC.  In fact, all the macro va_start,...
>are wrong for the sparc.  Who has build a right version of this header
>file?  

On this same topic, it seems worthy of note that users of any "binary only"
version of cfront should be very carful about using the right underlying
C compiler.

I learned recently that (contrary to my prior belief) you cannot simply
substitute *any* C compiler (e.g. GNU C) for the particular C compiler
that your (binary) copy of cfront was targeted for.  If you try to do that,
you may get into serious trouble because the "other" C compiler may have
a totally different way of handling so-called "varargs" functions.

Just a word to the wise.  Tread carefully.

-- 

// Ron ("Loose Cannon") Guilmette
// Internet: rfg@ncd.com      uucp: ...uunet!lupine!rfg
// New motto:  If it ain't broke, try using a bigger hammer.