http://llvm.org/bugs/show_bug.cgi?id=15206
Anton Korobeynikov <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED CC| |[email protected] Resolution|--- |INVALID --- Comment #10 from Anton Korobeynikov <[email protected]> --- (In reply to comment #9) > It is of course acceptable. This bug is not about stopping defining __GNUC__. > > This bug is about compatibility issues as a result of defining __GNUC__ and > what could be done to reduce the negative impact of this #define. Defining __GNUC__ is not connected with supporting all possible knobs and options of gcc (some of them are essentially implementation-defined), after all, different gcc versions have different cmdline options. Even more, the option in question does not influence the results of the test, so it should not be there after all (and it's somehow strange to use C++ compiler for C-level checks... what's about different inline semantics?). clang is not going to emulate MySQL configure checks' bugs, really. > For the same reasons "-Werror -fno-implicit-templates" should not produce > errors. It should. You explicitly ask for warning here. You got the warning. It's upgraded to error. This is how -Werror works. Please move such discussion to llvm-dev, bugzilla is an inappropriate place for this. -- You are receiving this mail because: You are on the CC list for the bug.
_______________________________________________ LLVMbugs mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs
