[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Selectively suppress -Wcast-function-type (issue 357770043 by addres

From: dak
Subject: Re: Selectively suppress -Wcast-function-type (issue 357770043 by address@hidden)
Date: Wed, 15 Aug 2018 15:09:55 -0700

On 2018/08/15 21:51:46, Dan Eble wrote:
On 2018/08/15 16:43:27, dak wrote:
> This is more a sort of logic nitpick than of actual relevance given
how GCC is
> wired, but if we want to be using -Wno-cast-function-type , that's
what we
> should announce and check for rather than -Wcast-function-type .

I couldn't figure out any other way to check for
reliably.  Attempts involving -Werror were defeated by the fact that
preprocessor variable is redefined somewhere, leading to an error in
all cases.
After spending much time to figure that much out, I was not interested
spending more to figure out how to resolve it (if that is even

I could reword the message, something like "whether the compiler might
about casting functions to incompatible types."  Would that be better?

I was "Huh?" until I tried out a few things.  g++ -Wno-blubber produces
no diagnostic while g++ -Wblubber bombs out.  Just add a comment like
# g++ -Wno-whatever compiles so we need to check for the positive option

because otherwise nobody will be able to guess what is up here.  In
general, what looks like a mistake or oversight and/or what just became
obvious through testing warrants a comment.  Don't keep things secret
between you and the compiler.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]