Eric Blake-1 wrote:
It depends on whether the warning was masking a bug or not. But you are
better off reporting such bugs to the upstream maintainers - oftentimes,
that warning indicates a true bug where someone has compiled on Linux and
used wchar_t when they should have used wint_t, but other times, it is
benign. What makes this particular error annoying is that there is no way
(except in CVS gcc) to disable it when it is a false positive, and
restructuring the comparison to avoid the warning can sometimes be rather
difficult.
So, to whom I should report about these warnings to get
skilled suggestions for fast fixing or confirmations for safely ignoring it? Anybody can
really help ? Thanks a lot.
