------- Comment #6 from geoffk at gcc dot gnu dot org 2006-08-21 23:22 ------- The same thing happens if you use 'file.i' rather than 'file.h': it gets treated as preprocessed rather than C++ source:
$ ./g++ -B./ -c -x c++ file.i -### Reading specs from ./specs Target: i386-apple-darwin9.0.0d2 Configured with: /Volumes/Data/co/gcc-trunk/configure Thread model: posix gcc version 4.2.0 20060818 (experimental) "./cc1plus" "-fpreprocessed" "file.i" "-fPIC" "-quiet" "-dumpbase" "file.i" "-mtune=i386" "-auxbase" "file" "-o" "/var/tmp//ccztNIJB.s" "./as" "-arch" "i386" "-force_cpusubtype_ALL" "-o" "file.o" "/var/tmp//ccztNIJB.s" If someone has a built FSF 3.3 around, it would be good if they could check whether this behaviour persists there. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28528
