Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!mcsun!ukc!axion!uzi-9mm.fulcrum.bt.co.uk!sie From: sie@fulcrum.bt.co.uk (Sie) Newsgroups: comp.sys.amiga.programmer Subject: Re: SAS C 5.10A has problems Message-ID: Date: 25 Jun 91 13:38:27 GMT References: <1991Jun24.110845.19273@forwiss.uni-passau.de> Sender: news@fulcrum.bt.co.uk (News with an UZI) Organization: Fulcrum Communications Ltd., Birmingham, England Lines: 28 In-Reply-To: hessmann@unipas.fmi.uni-passau.de's message of 24 Jun 91 11: 08:45 GMT >>>>> On 24 Jun 91 11:08:45 GMT, hessmann@unipas.fmi.uni-passau.de (Georg Hessmann) said: Georg> Nntp-Posting-Host: unipas.fmi.uni-passau.de Georg> In article mykes@amiga0.SF-Bay.ORG (Mike Schwartz) writes: >Problem #2: When compiling some sources, I get CXERR: 99, which is >NOT documented in the manual. Nice messages, eh folks? Real >descriptive :) The compiler does not complain about anything else in >the source file. This error comes up during the Optimizing phase. Georg> I've got this message, too. The reason was a varargs Georg> function. If you use varargs functions with the 'va_list' Georg> type, try two things: First, declare the funktion as __stdargs Georg> and second, declare the 'va_list' variable as 'volatile'. Georg> E.g.: void __stdargs Message(char *fmt, ...) { volatile Georg> va_list list: ... } This can't be the problem, I use varargs all the time and have not had to do any of these things to make it compile ?? -- Simon J Raybould (sie@fulcrum.bt.co.uk) // {o.o} "Only joking ... Or am I ?" - Vic Reeves \X/AMIGA \-/ =========================================================================== Fulcrum communications L.T.D., Fordrough Lane, Birmingham, B9 5LD, ENGLAND.