Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!tecate.mips.com!trevc From: trevc@tecate.mips.com (Trevor Cotton) Newsgroups: comp.sys.sgi Subject: Re: C compiler question Message-ID: <2966@spim.mips.COM> Date: 2 May 91 20:46:25 GMT References: <48295@ut-emx.uucp> Sender: news@mips.COM Reply-To: trevc@mips.com Organization: Mips Computer Systems Inc., Sunnyvale, CA Lines: 26 Nntp-Posting-Host: tecate.mips.com In article <48295@ut-emx.uucp>, dboles@ccwf.cc.utexas.edu (David Boles) writes: |> I am having a problem with the MIPS C compiler. When I compile, |> I use the command cc -acpp -prototypes -p0. The p0 is there because |> the C compiler seems to get confused and generates profiling info. |> The main problem is that the -prototype option doesn't work correctly. |> There are no warnings generated when I compile code in which the |> function prototype does not match its definition! I can get by with |> just the acpp preprocessor for my macros, but function prototyping |> provides a very powerful way to keep your code healthy. |> |> Any comments? When is MIPS C going to be real C (i.e. ANSI)? |> |> |> -- |> ------------------------------------------------------------------------------- |> David Boles Applied Research Laboratories |> dboles@ccwf.cc.utexas.edu DOS is severely brain-damaged, |> apas611@chpc.utexas.edu so just pull the plug and let it DIE. |> ------------------------------------------------------------------------------- MIPS ANSI-CC release 2.20 is available now as an optional product for the MIPS line of systems. As to when SGI will make this available, I cannot comment. -- --trevc--