On Sat, Feb 28, 2009 at 06:27:17AM -0700, Eric Blake wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > According to Tom G. Christensen on 2/27/2009 2:19 PM: > > On Fri, Feb 13, 2009 at 11:21:11AM +0100, Simon Josefsson wrote: > >> How does that work? Do most compilers out there really support > >> decl-after-stmt (not likely?!)? > >> > > MIPSpro <anyversion> on IRIX in C89 mode doesn't like decl-after-stmt. > > Are there any command-line switches to the C89 compiler, though, that will > allow parsing a decl-after-stmt? > Good question but looking over the manpage for cc 7.4.4m I don't see anything useable. It has options like -diag_warning that can be used to turn errors into warnings but it does not seem to want to change the decl-after-stmt error (error#1241) into a warning. Similar -diag_error can be used to turn a warning into an error, most commonly used with error#1035 which makes cc honor the #error directive. The manpage can be seen on SGI techpubs here (long url): http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi?coll=0650&db=man&fname=/usr/share/catman/u_man/cat1/cc.z
A guide to MIPSPro pragmas can be seen on SGI techpubs here (long url): http://techpubs.sgi.com/library/tpl/cgi-bin/browse.cgi?coll=0650&db=bks&cmd=toc&pth=/SGI_Developer/Pragmas > Even if such switch is the one that > enables C99 mode? > MIPSPro 7.4.x has a C99 mode (c99 or cc -c99) and has no problems with decl-after-stmt in C99 mode. Earlier versions including MIPSPro 7.2.x/7.3.x on IRIX 6.x has no C99 mode and no switch that I can find to allow decl-after-stmt. > Or put another way, you aren't stuck in a situation > where the only compiler on your system can't handle decl-after-stmt? > No on IRIX you always have the option of installing GCC. MIPSPro is known to create better code than GCC, for most tasks it doesn't matter so much but for some performance critical things the difference can be dramatic. MIPSpro is also a much faster compiler than GCC 4. -tgc
