This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: g++ no longer ignoring some warning flags?
- To: pfeifer at dbai dot tuwien dot ac dot at
- Subject: Re: g++ no longer ignoring some warning flags?
- From: Marc Espie <espie at quatramaran dot ens dot fr>
- Date: Thu, 30 Sep 1999 23:24:46 +0200
- Cc: egcs-bugs at egcs dot cygnus dot com
- Organization: Ecole Normale Superieure de Paris
- References: <199909231410.KAA09566@caip.rutgers.edu>
In article <Pine.GSO.4.10.9909231735320.9492-100000@markab.dbai.tuwien.ac.at> you write:
>On Thu, 23 Sep 1999, Kaveh R. Ghazi wrote:
>> I used to be able to bootstrap with special WARN_CFLAGS and
>> when g++ was run, it ignored the irrelevant ones. Now I get an error
>> during bootstrap:
>>
>>> cc1plus: Invalid option `-Wstrict-prototypes'
>>> cc1plus: Invalid option `-Wmissing-declarations'
>>> cc1plus: Invalid option `-Wmissing-noreturn'
>>> cc1plus: Invalid option `-Wtraditional'
>>> cc1plus: Invalid option `-Wbad-function-cast'
>>> make[5]: *** [tinfo.o] Error 1
>>
>> This had worked as recently as Friday, 9/17.
>>
>> Can we please restore the old behavior?
>
>Please don't!
>With the old behavior g++ would simply ignore these unsupported options
>silently, making the user believe that they *were* actually supported.
Err... some of these ARE implemented by g++. In fact, you can't
turn -Wstrict-prototypes -Werror off...