g++ "looses" options?

Jeffrey A Law law@cygnus.com
Thu Sep 30 19:57:00 GMT 1999


  In message <Pine.GSO.4.10.9909211842050.24676-100000@vexpert.dbai.tuwien.ac.a
t>you write:
  > Today I noticed that with a g++ from current CVS I get the following from
  > some legacy project here:
  > 
  >  cc1plus: Invalid option `-Wtraditional'
  >  cc1plus: Invalid option `-Wbad-function-cast'
  >  cc1plus: Invalid option `-Wnested-externs'
  >  cc1plus: Invalid option `-Wstrict-prototypes'
  >  cc1plus: Invalid option `-ftemplate-depth-20'
  > 
  > Is this a result of the recent option processing rewrite by Nick(?) ?
Likely. 

  > Have these always been C-only options which are now correctly rejected
  > by the C++ frontend?
Also likely.  That was the case I found when libobjc wouldn't build today.
We were passing an Objective-C option to the C compiler, that's an error now
rather than a silent acceptance.

 > Why does -ftemplate-depth not exist any longer?
Not a clue.  This sounds like a real bug.


jeff




More information about the Gcc-bugs mailing list