On Thursday, 25 May 2017 13:32:54 PDT Thiago Macieira wrote: > We're testing __EXCEPTIONS, like we should. > > Please describe the environment in which: > a) -fno-exceptions is active > b) __EXCEPTIONS is defined > > Provide the full command-line and the compiler version. > > I still advise you to look into what's wrong with your testing, because I > can't reproduce it.
Ok, I could reproduce this. It's Apple's bug and regression. $ /Applications/Xcode.app/Contents/Developer/Toolchains/ XcodeDefault.xctoolchain/usr/bin/clang++ -fno-exceptions -std=c++11 -dM -E - xobjective-c++ /dev/null | grep __EXCEPTIONS #define __EXCEPTIONS 1 $ /Applications/Xcode6.4.app/Contents/Developer/Toolchains/ XcodeDefault.xctoolchain/usr/bin/clang++ -fno-exceptions -std=c++11 -dM -E - xobjective-c++ /dev/null | grep __EXCEPTIONS [nothing] Please report to Apple. This problem does not exist upstream and did not exist in previous releases of their Clang. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
