I am back for some news : I might confirm some bugs I suspected one month ago.
By the way, I had this compiler flags pane bug too with Win8.1 x64 Pro and the nightly of October. I did not play with compilers with the last nightly so no bug yet.
For the bugs I suspected, it concerns CC and MinGW auto set macros. I will say bug but maybe I am wrong and I just misused the IDE.
I use MinGW 4.9.2 x86 dw2 POSIX (the one with Qt) but these bugs happens even with other versions (like the 4.7.1 TDM) and the build I use is 10595.
When I set a project to be C++11 in build options, i check the C++11 flag in the root build options.
But when I start to write __cpluplus and use CC, it says that the value is still 199711L so the c++11 features are not present in CC.
I tried to save the project, reparse it or even close and reload the project. The bug is still here.
The only workaround I found is to close C::B and restart the whole software to have the right value 201103L, the good macros conditions and have c++11 features in CC.
When I use predefined macros, CC does not process properly the conditions.
It says for example that __WIN32__ = 1 or __WIN32 = 1
but when I write
The foo is still grayed, disabled. (of course the compilation works fine). But this time I did not find a 'good' workaround. I have to redefine the macro in custom defines tab, which is ugly :p ... And I have to close-reopen the project so that CC take in account the new defines.
Here are the screens for the C++11 issue but as you can see it is a more general bug with macro definitions, I will add screens for __WIN32 in another answer as we are limited to 2 screens per post :