compiler-warnings

I know these warnings are probably pointless.. But anyway I could get rid of them? I got 7 of these warnings. Bitwise-or operator used on a sign-extended operand; consider casting to a smaller unsigned type first This has something to do with the OR operator | I highlighted what gives off the warnings. int result = (int)ror((uint)(v76 ^ (v75 | 0x862D63D3)), (uint)(BitConverter.ToInt32(v4, 72) ^ 0x22)); int v11 = (int)rol((uint)(int)((v8 & v10 | ~v10 & 0xEFCDAAC9) + v3[2] - 1126481991), 17); int v144 = (int)rol((uint)(int)((v141 & v143 | ~v143 & 0xEFCDAAC9) + v3[2] - 1126481991), 17); int v77 =

Does anyone know of any warnings that C++ compilers provide that help to enforce const correctness? For instance, it would be nice to have a warning produced by any C++ method that contains a non-const parameter that is never modified inside of the method. I see that there is a gnu compiler warning called -Wsuggest-attribute=const; however, when I use this flag I get an error saying that it is not recognized. Any ideas why? I don't think such a warning exists, mostly because it would be useless. Just because a parameter is not modified inside the call, doesn't mean it should be made const just

So I am getting- warning: [options] bootstrap class path not set in conjunction with -source 1.6 And I am about to ask 3 questions about it. I understand that I need to set the bootstrap class path but I am not sure I understand how. A quick google just sent me to pages that quoted from the Oracle page, but I read the Oracle page and didn't feel that I understood it particularly well. I am currently running this code on Netbeans, so all I have to do is hit the play button for it to compile and run. Is there a property that dictates how this will compile so that I may add in the bootstrap class

The following is nonsensical yet compiles cleanly with g++ -Wall -Wextra -Werror -Winit-self (I tested GCC 4.7.2 and 4.9.0): #include <iostream> #include <string> int main() { for (int ii = 0; ii < 1; ++ii) { const std::string& str = str; // !! std::cout << str << std::endl; } } The line marked !! results in undefined behavior, yet is not diagnosed by GCC. However, commenting out the for line makes GCC complain: error: ‘str’ is used uninitialized in this function [-Werror=uninitialized] I would like to know: why is GCC so easily fooled here? When the code is not in a loop, GCC knows that it is

In Xcode 5, is there any way to suppress warnings such as unused variables for number of files? Particularly latest Box2D 2.2.1 produces some warnings which are annoying but harmless. Select the project in the navigator, then select the target from the list. Select the Build Phases tab, then expand the Compile Sources phase. The Compiler Flags column is where you specify per-file compiler flags. Enter -Wno- to negate a warning. e.g.: -Wno-unused-parameter You can add a compiler flag -w for each affected .m file you want silenced, in the build phases for your app's target, under "Compile

When you compile the following C++ source file in Visual Studio 2010 with warning level /W4 enabled #include <cstdio> // for printf #include <cstring> // for strcmp char str0[] = "Hello"; char str1[] = "World"; int main() { int result; if (result = strcmp(str0, str1)) // line 11 { printf("Strings are different\n"); } } you get the following warning warning C4706: assignment within conditional expression for line 11. I want to suppress this warning exactly at this place. So I tried Google and found this page: http://msdn.microsoft.com/en-us/library/2c8f766e(v=VS.100).aspx So I changed the code