Welcome!
What's the idea?
The idea of this site is to have a list of preferably all possible warnings and errors of C compiler with the description of real problems, which have produced them. The reason is because the warning/error official description sometimes seems misleading or doesn't correspond to actual problem. Hopefully it could save up some time in the future anybody reading it, while debugging tough cases.
Why not to use stackoverflow?
The idea of stackoverflow is to find a solution through discussion of all sorts of problems in the code. Although you can find a lot of dicussions useful and also find a solution - you still need time to read all the posts and evaluate what is written there. Reading all of them might be required, as you can get the same warning/error for different problems in the code. Also there might be solutions distributed between stackoverflow posts. This site only specifically deals with warnings and errors of C compiler. And it specifies the different reasons you might have for the same warning/error in one blog post. I hope it is much quicker to look here first. Although if none of the reasons correspond to your problem I encourage you to check stackoverflow for more wider and deeper analysis. Every post at the end has a link to the post topic on stackoverflow. If you then find the solution there, please do not hesistate to leave it in comments of particular warning/error or send it to "compilerwarnings @ gmail . com".
Why is it important?
In the past I have underestimated warnings and their implact on the quality of the code and time spent on the debugging. But I realised that it really saves time and makes code more robust. Programmer shall always address them when writing the code, either as a job task or for a personal project.
How do you know the reasons you describe?
It works like that: if I get a warning or error during compiling of my work projects I look to reasons and solutions an then describe it here in the blog post dedicated for particular warning or error number. This way I ensure the reason and solution are right before posting here.
Is there a complete list available?
The list of available warnings and errors, can be found from top menu items with similar names. While I'm doing it alone it will not be fast while the list becomes complete and usefull for most of the people. Hopefully I address the most frequent problems first. But the kind of warnings and errors I get during my work also depends on my coding style. It means that people with different experience level will be most likely getting other warnings more often. If you find this effort useful you can really help!
Can I help?
If you see a warning or error, which already have a blog post, but doesn't describe your particular problem - please add it to the comments. I will try my best to transfer your description from comments to the post to make things faster to read. In case you have discovered a warning/error, which doesn't have a description yet - just send a description of the particular problem, which caused it to "compilerwarnings @ gmail . com" and I will add it as soon as possible.
Together we can make coding - faster and easier process for everyone!