Failing to return a value from a function that has a non-void return type results in undefined behaviour, but is not a semantic error. The reason for this, as far as I can determine, is largely historical. C originally didn’t have void and implicit int meant that most functions returned an int unless explicitly declared … Read more
Use -Wconversion — the problem is an implicit cast (conversion) from long x to short when the function f(short x) is called [not printf], and -Wconversion will say something like “cast from long to short may alter value”. .. Edit: just saw your note. -Wconversion results in a warning for me, using g++ 4.3.2 on … Read more
Yes, it is possible to avoid reporting undefined references – using –unresolved-symbols linker option. g++ mm.cpp -Wl,–unresolved-symbols=ignore-in-object-files From man ld –unresolved-symbols=method Determine how to handle unresolved symbols. There are four possible values for method: ignore-all Do not report any unresolved symbols. report-all Report all unresolved symbols. This is the default. ignore-in-object-files Report unresolved symbols that … Read more
It’s hard to say it’s a bug, because gcc mixes up code for optimization and for creating warnings, which is even documented for this particular warning: -Wuninitialized Warn if an automatic variable is used without first being initialized or if a variable may be clobbered by a setjmp call. […] Because these warnings depend on … Read more
GCC’s -Weffc++ has several issues, I never use it. The code that checks for “problems” is pretty simplistic and so the warnings end up being far too blunt and unhelpful. That particular warning is based on Item 11 of the first edition of Effective C++ and Scott changed it (for the better) in later editions. … Read more
It is actually possible to disable specific warnings on the device with NVCC. It took me ages to figure out how to do it. You need to use the -Xcudafe flag combined with a token listed on this page. For example, to disable the “controlling expression is constant” warning, pass the following to NVCC: -Xcudafe … Read more
Use the C# commandline option /nowarn http://msdn.microsoft.com/en-us/library/7f28x9z3(VS.80).aspx To do this within visual studio goto Project properties->Build->(Errors and warnings) Suppress Warnings and then specify a comma separated list of warnings which need to be suppressed.
If you really, really must do this, and you are sure you are not making a mistake, check out the @SuppressWarnings annotation. I suppose in your case you need @SuppressWarnings(“fallthrough”) Is the annotation @SuppressWarnings (javadoc) what you are looking for? For example: @SuppressWarnings(“unchecked”) public void someMethod(…) { … }
This is not a bug, but “feature“: For a string, dynamic array, method pointer, or variant result, the effects are the same as if the function result were declared as an additional var parameter following the declared parameters. In other words, the caller passes an additional 32-bit pointer that points to a variable in which … Read more
Yes. For disabling, use: #pragma warning disable 0169, 0414, anyothernumber Where the numbers are the identifiers of the warnings that you can read from compiler output. To reenable the warnings after a particular part of code (which is a good idea) use: #pragma warning restore 0169, anythingelse This way you can make the compiler output … Read more