This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: How to make 'control reaches end of non-void function' a fatal error ?
- To: mk at baerlap dot north dot de, Jan Dvorak <johnydog at go dot cz>
- Subject: Re: How to make 'control reaches end of non-void function' a fatal error ?
- From: russ at amc dot com (Russell Browne)
- Date: Fri, 25 Aug 2000 15:44:27 -0700
- Cc: gcc at gcc dot gnu dot org
>
> Thanks, i missed -Werror. This would be a good solution. I also think
> that every warning is one warning too much. Unfortunately i have to deal
> with automatically generated code. I'm rather sure that i will not be
> able to get rid of _all_ warnings. It's possible to selectively disable
> some warnings. I'll see how far i get with this - but i don't like
> it. I _know_ how live goes. Today you disable a warning, tomorrow it
> will finally kill you. I fear i will have to go with grep if there is
> no other solution.
My first choice would be to fix the code generator to write code
that gcc -Wall likes.
My second choice would be to give the generated files a different suffix
than the manually coded ones (.cxx and .cc for example), or put the
generated files in a separate directory, and set up make to turn
off -Werror for the generated files.
Russ Browne
Applied Microsystems Corp.