--- 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
--- Comment #5 from janis at gcc dot gnu dot org 2006-08-21 21:20 ---
A regression hunt on powerpc-linux identified this patch, which is a merge of
the pch-branch:
http://gcc.gnu.org/viewcvs?view=rev&rev=61136
r61136 | geoffk | 2003-01-10 02:22:34 + (Fri, 10 Jan 2003)
If i
--- Comment #4 from pinskia at gcc dot gnu dot org 2006-08-18 04:52 ---
(In reply to comment #3)
> Also, removing the space between '-x' and 'c++' works, eg,
You are correct, weird.
Actually:
g++ -c -x c++ t.h
fails too:
--output-pch=t.h.gch
--
http://gcc.gnu.org/bugzilla/show_bu
--- Comment #3 from dannysmith at users dot sourceforge dot net 2006-08-18
04:48 ---
Also, removing the space between '-x' and 'c++' works, eg,
g++ -fsyntax-only -xc++ stdio.h
but I get warning
warning: #pragma system_header ignored outside include file
ditto with
g++ -c -x c++ std
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-08-18 04:06 ---
Confirmed, it did not work in 3.4.0 which almost means this was caused by the
PCH changes.
Janis could you do a regression hunt on this one. The best way I guess to do
this is to put "int main(void){}" in a .h file.
--
mmitchel at gcc dot gnu dot org changed:
What|Removed |Added
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28528
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-07-29 05:27 ---
I think the behavior changed in 3.4 with the additional of PCH but I need to
double check what happens in 3.4.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28528
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
CC||pinskia at gcc dot gnu dot
|
