bothner@sevenlayer.cs.wisc.edu (Per Bothner) (01/21/91)
In article <1991Jan17.123851.26892@dde.dk> cfj@dde.dk (Claus Fjell Jensen) writes: >Hello world - I have a number of questions concerning the G++ and >GCC GNU products. > > o How does the current ver. 1.37.0 GNU C++ conform to the new > ANSI X3J16 committee C++ draft standard, as described in The > Annotated C++ Reference Manual by Margaret A. Ellis and Bjarne > Stroustrup. No compiler conforms to the ARM (which is NOT a draft standard - no such has been released). Both cfront 2.1 and g++ are close, and working on becoming closer. As you could expect, the former is closer - but they sort of have an unfair advantage... All major C++ compilers writers are committed to conformance with the eventual standard. > o The GCC compiler has an naming convention that precedes > all names in the assembler code by underscores No, it doesn't. *Unix* traditionally has such a naming convention. Gcc on most machines follows this, for compatibility. The mips port of gcc does not prepend underscores. > o There is a patch for GCC that makes it produce COFF format > object modules. This is again misleading. Gcc invokes an assembler to produce object files. To produce COFF/ECOFF, use an assembler that produces those formats - e.g. use /bin/as. The Mips port of gcc produces ECOFF. The real issue is debugging symbols. The OSF port of gcc (available on foobar.colorado.edu) can generate ECOFF debugging symbols for gdb or dbx. However, it's a kludge, and doesn't really work for g++, partly because ECOFF doesn't (yet) support C++ data types. The plan is to produce a mips port of gas (the GNU assembler) that emits dbx-style stabs debugging information. Various pieces of the solution exist, but it may still take a while before we have something decent. > o Has anybody tried to mix the G++ and the AT&T C++ environments > and are there (m)any pitfalls in doing this. Unlcear question. It is possible to write programs that work with both compilers (and it may be a good disciple). However, you can't link g++ object files with those produced by cfront, partly because of different name mangling conventions. > o Will it be possible, with the old or the new version of G++, > to compile ALL class-libraries written in AT&T C++ 2.1 style code. Not with with g++-1.37. You may come close with g++-2.0, though I'd be surprised if you didn't have to do some slight editing. -- --Per Bothner bothner@cs.wisc.edu Computer Sciences Dept, U. of Wisconsin-Madison