Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!uunet!mcsun!ukc!icdoc!iwm From: iwm@doc.ic.ac.uk (Ian Moor) Newsgroups: comp.sys.amiga.programmer Subject: Re: REVIEW: Comeau C++ compiler Message-ID: Date: 24 Apr 91 14:38:39 GMT Article-I.D.: swan.IWM.91Apr24153839 References: <1540@tronsbox.xei.com> <36963@ditka.Chicago.COM> <1991Apr17.174759.16250@jato.jpl.nasa.gov> <37123@ditka.Chicago.COM> Organization: Department of Confusion, Imperial College, London UK Lines: 26 In-Reply-To: comeau@ditka.Chicago.COM's message of 19 Apr 91 18:46:21 GMT In article <37123@ditka.Chicago.COM> comeau@ditka.Chicago.COM (Greg Comeau) writes: . From my discussion with other compiler writers as well as my own feelings, there is very little that say a direct native code compiler could do better, and when it can, it usually comes down One problem with using a fairly complex language as an intermediate code, especially when the `backend' is error reporting. As a case in point, I am evaluating a Modula-2 compiler for SPARC that produces C, I get an error message from Sun's C compiler about an intermediate file: is it a bug in the C compiler, or has the modula compiler generated incorrect C? The intermediate code is not meant to be read, and I have to assume the modula compiler is wrong, since GCC does not like the file either. You may find with the different C compilers SAS/Lattice/PDC/DICE/GCC... that one will work and the others not. -- Ian W Moor Internet: iwm@doc.ic.ac.uk JANET: iwm@uk.ac.ic.doc Department of Computing, Lecturer,n. One with his hand in your pocket, Imperial College. his tongue in your ear, and his faith in your 180 Queensgate patience. London SW7 UK. Ambrose Bierce.