I usually encourage students to compile their projects with the -wall option to catch a lot of 'newbie' errors.
While this may generate some noise it also helps catch some common errors.
Unfortunately when using PE it generates a lot of noise. While I have no reason to believe these are actual errors it would be better if there wasn't so much clutter.
Can I ask you to consider auditing your software for common items that trigger these warning? You never know it might actually find some bugs.
An example of code that produces a warning (from startup.c):
../Project_Settings/Startup_Code/startup.c:85:62: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] else if( !(src & mask_short) && !(dst & mask_short) && len >= size_short)